Lock screen interface for a mobile device apparatus

ABSTRACT

In various embodiments, different mobile phones are provided, comprising: a touchscreen including a backlight; a near field communication interface; at least one non-transitory memory storing instructions; and one or more processors in communication with the touchscreen, the near field communication interface, and the at least one non-transitory memory, wherein the one or more processors execute the instructions to initiate various capabilities and/or functionalities in connection with a lock screen displayed on the touchscreen.

RELATED APPLICATIONS

The present application is a continuation of and claims priority toapplication Ser. No. 15/789,867 filed on Oct. 20, 2017 which, in turn,is a continuation-in-part of and claims priority to application Ser. No.14/050,332 filed on Oct. 9, 2013 which, in turn, claims priority toApplication No. 61/722,122 filed Nov. 2, 2012, which are allincorporated herein by reference.

FIELD OF THE INVENTION AND BACKGROUND

The present invention relates to mobile devices, and more particularlyto mobile device lock screen interfaces.

SUMMARY

In one embodiment, a mobile phone is provided, comprising: a touchscreenincluding a backlight; a near field communication interface; amechanical button; at least one non-transitory memory storinginstructions; and one or more processors in communication with thetouchscreen, the near field communication interface, the mechanicalbutton, and the at least one non-transitory memory, wherein the one ormore processors execute the instructions to: receive, from a terminalutilizing the near field communication interface of the mobile phone, anear field communication signal; determine whether the mobile phone isoperating in a lock screen mode; determine whether the backlight of thetouchscreen of the mobile phone is powered off; in response to thereceipt of the near field communication signal from the terminalutilizing the near field communication interface of the mobile phonewhen the backlight of the touchscreen of the mobile phone is determinedto be powered off: power on the backlight of the touchscreen of themobile phone; in response to the receipt of the near field communicationsignal from the terminal utilizing the near field communicationinterface of the mobile phone when the mobile phone is determined to beoperating in the lock screen mode, and without necessitating any userinput into the mobile phone after the receipt of the near fieldcommunication signal from the terminal utilizing the near fieldcommunication interface of the mobile phone: simultaneously display, viathe touchscreen of the mobile phone, at least one card, at least aportion of a card number of the at least one card, and an indication toenter a touch user input via the mechanical button of the mobile phone;after the display, via the touchscreen of the mobile phone, of the atleast one card, the at least portion of the card number of the at leastone card, and the indication to enter the touch user input via themechanical button of the mobile phone: receive an indication of thetouch input via the mechanical button of the mobile phone; withoutnecessitating any user input into the mobile phone other than the touchuser input via the mechanical button of the mobile phone and apresentation of a face of a user after the display, via the touchscreenof the mobile phone, of the at least one card, the at least portion ofthe card number of the at least one card, and the indication to enterthe touch user input via the mechanical button of the mobile phone:capture the face, utilizing the mobile phone; in response to the captureof the face utilizing the mobile phone, perform an analysis based on thecapture of the face, and based on the analysis, send, to the terminalutilizing the near field communication interface of the mobile phone, anauthorization signal; and after sending, to the terminal utilizing thenear field communication interface of the mobile phone, theauthorization signal: receive a response signal, and in response to thereceipt of the response signal: display, via the touchscreen of themobile phone, a notification indicating whether use of the at least onecard was successful.

In another embodiment, a mobile phone is provided, comprising: atouchscreen including a backlight; a near field communication interface;at least one non-transitory memory storing instructions; and one or moreprocessors in communication with the touchscreen, the near fieldcommunication interface, and the at least one non-transitory memory,wherein the one or more processors execute the instructions to: receive,from a terminal utilizing the near field communication interface of themobile phone, a near field communication signal; determine whether themobile phone is operating in a lock screen mode; determine whether thebacklight of the touchscreen of the mobile phone is powered off; inresponse to the receipt of the near field communication signal from theterminal utilizing the near field communication interface of the mobilephone when the backlight of the touchscreen of the mobile phone isdetermined to be powered off: power on the backlight of the touchscreenof the mobile phone; in response to the receipt of the near fieldcommunication signal from the terminal utilizing the near fieldcommunication interface of the mobile phone when the mobile phone isdetermined to be operating in the lock screen mode, and withoutnecessitating any user input into the mobile phone after the receipt ofthe near field communication signal from the terminal utilizing the nearfield communication interface of the mobile phone: simultaneouslydisplay, via the touchscreen of the mobile phone, at least one card, atleast a portion of a card number of the at least one card, and anindication to scan a fingerprint via the mobile phone; withoutnecessitating any user input into the mobile phone other than afingerprint scan user input after the display, via the touchscreen ofthe mobile phone, of the at least one card, the at least portion of thecard number of the at least one card, and the indication to scan thefingerprint via the mobile phone: scan the fingerprint, utilizing themobile phone; in response to the scan of the fingerprint utilizing themobile phone, perform an analysis based on the scan of the fingerprint,and based on the analysis, send, to the terminal utilizing the nearfield communication interface of the mobile phone, an authorizationsignal; and after sending, to the terminal utilizing the near fieldcommunication interface of the mobile phone, the authorization signal:receive a response signal, and in response to the receipt of theresponse signal:display, via the touchscreen of the mobile phone, anotification indicating whether use of the at least one card wassuccessful.

In other embodiments, other mobile phones are provided that omit one ormore of the features mentioned hereinabove, and possibly include otherfeatures disclosed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a network architecture, in accordance with oneembodiment.

FIG. 2 shows a representative hardware environment that may beassociated with the servers and/or clients of FIG. 1, in accordance withone embodiment.

FIG. 3 shows a method for a mobile device transaction, in accordancewith one embodiment.

FIG. 4 shows a system for mobile device transactions, in accordance withanother embodiment.

FIG. 5 shows a system for presenting advertisements/content, inaccordance with another embodiment.

FIG. 6 shows exemplary interfaces for configuring and/or registeringadvertisement/content triggers, in accordance with another embodiment.

FIG. 7 shows a system flow for presenting advertisements, in accordancewith another embodiment.

FIG. 8 shows a method for communicating advertisement/content triggerIDs, in accordance with one embodiment.

FIG. 9 shows a system for mobile device transactions, in accordance withanother embodiment.

FIG. 10 shows a method for a mobile device transaction, in accordancewith another embodiment.

FIG. 11 shows a method for a mobile device transaction, in accordancewith another embodiment.

FIG. 12 shows a method for a mobile device transaction, in accordancewith another embodiment.

FIG. 13 shows a system flow for presenting advertisements, in accordancewith another embodiment.

FIG. 14 shows a mobile device interface for facilitating a payment, inaccordance with another embodiment.

FIG. 15 shows a mobile device interface for facilitating a payment, inaccordance with another embodiment.

FIG. 16 shows a mobile device interface for facilitating a payment, inaccordance with another embodiment.

FIG. 17 shows a mobile device interface for facilitating a payment, inaccordance with another embodiment.

FIG. 18 shows a mobile device interface for presenting post-paymentfunctionality, in accordance with another embodiment.

DETAILED DESCRIPTION

FIG. 1 illustrates a network architecture 100, in accordance with oneembodiment. As shown, a plurality of networks 102 is provided. In thecontext of the present network architecture 100, the networks 102 mayeach take any form including, but not limited to a local area network(LAN), a wireless network, a wide area network (WAN) such as theInternet, peer-to-peer network, etc.

Coupled to the networks 102 are servers 104 which are capable ofcommunicating over the networks 102. Also coupled to the networks 102and the servers 104 is a plurality of clients 106. Such servers 104and/or clients 106 may each include a desktop computer, lap-topcomputer, hand-held computer, mobile phone, personal digital assistant(PDA), peripheral (e.g. printer, etc.), any component of a computer,and/or any other type of logic. In order to facilitate communicationamong the networks 102, at least one gateway 108 is optionally coupledtherebetween.

FIG. 2 shows a representative hardware environment that may beassociated with the servers 104 and/or clients 106 of FIG. 1, inaccordance with one embodiment. Such figure illustrates a typicalhardware configuration of a workstation in accordance with oneembodiment having a central processing unit 210, such as amicroprocessor, and a number of other units interconnected via a systembus 212.

The workstation shown in FIG. 2 includes a Random Access Memory (RAM)214, Read Only Memory (ROM) 216, an I/O adapter 218 for connectingperipheral devices such as disk storage units 220 to the bus 212, a userinterface adapter 222 for connecting a keyboard 224, a mouse 226, aspeaker 228, a microphone 232, and/or other user interface devices suchas a touch screen (not shown) to the bus 212, communication adapter 234for connecting the workstation to a communication network 235 (e.g., adata processing network) and a display adapter 236 for connecting thebus 212 to a display device 238.

The workstation may have resident thereon any desired operating system.It will be appreciated that an embodiment may also be implemented onplatforms and operating systems other than those mentioned. Oneembodiment may be written using JAVA, C, and/or C++ language, or otherprogramming languages, along with an object oriented programmingmethodology. Object oriented programming (OOP) has become increasinglyused to develop complex applications.

Of course, the various embodiments set forth herein may be implementedutilizing hardware, software, or any desired combination thereof. Forthat matter, any type of logic may be utilized which is capable ofimplementing the various functionality set forth herein.

FIG. 3 shows a method 300 for a mobile device transaction, in accordancewith one embodiment. As an option, the method 300 may be implemented inthe context of the architecture and environment of the previous Figuresand/or any subsequent Figure(s). Of course, however, the method 300 maybe carried out in any desired environment.

As shown, an indication is received that a mobile device has establishedcommunication with a point-of-sale terminal. See operation 302. Further,in immediate response to the receipt of the indication, indicia isdisplayed for prompting user input to allow a transaction to occur inresponse thereto. See operation 304.

In the context of the present description, a point-of-sale terminalrefers to any terminal capable of facilitating a sale between entities.For example, in one embodiment, the point-of-sale terminal may include apoint-of-sale terminal located a retailer location (e.g. a departmentstore, a grocery store, a restaurant, a service center, a fuelingstation, etc.). As an option, the point-of-sale terminal may or may notbe equipped with a cash register, inventory management system, etc.

The mobile device may include any type of mobile device. For example, invarious embodiments, the mobile device may include a mobile phone, atablet computer, an e-reader, a PDA, a handheld computer, a media device(e.g. a digital music player, a digital video player, etc.), and/or anyother type of device that is mobile, for that matter.

The communication between the mobile device and the point-of-saleterminal may include various types of communication. For example, in oneembodiment, the communication may be established utilizing near fieldcommunication (NFC). In another embodiment, the communication may beestablished utilizing Wi-Fi functionality (e.g. Wi-Fi direct, etc.). Inanother embodiment, the communication may be established utilizingBluetooth functionality. In another embodiment, the communication may beestablished utilizing bump technology (e.g. direct contact, etc.). Forexample, in one embodiment, such bump technology may or may not includeone or more of the features set forth in U.S. Application PublicationNo.: US2011/0191823A1 filed Feb. 3, 2010, which is incorporated hereinby reference for all purposes. In still yet another embodiment, thecommunication may be established via the Internet (e.g. via a cellularnetwork, Wi-Fi network, etc.).

The indication may be received in a various ways. For example, in oneembodiment, the indication may be received based on a physical contactbetween the mobile device and the point-of-sale terminal. In this case,in one embodiment, the physical contact may be detected utilizing bumptechnology. In another embodiment, the indication may be received inresponse to an exchange of information via any of the aforementionedcommunication techniques (e.g. Wi-Fi, cellular, Internet, etc.).

For instance, in one possible embodiment, a service (administered, forexample, by an application on the mobile phone and software at thepoint-of-sale) may determine that a first dynamic location of the mobiledevice being determined to be the same (or within a predetermineddistance) as a second predetermined location of the point-of-saleterminal. Upon such determination, the service may send an indicationsignal to the mobile device (e.g. via the application).

In one embodiment, in connection with the indication, transactioninformation may or may not be received by the mobile device from thepoint-of-sale terminal. Additionally, in one embodiment, suchtransaction information may be displayed simultaneously with theindicia. The transaction information may include any informationassociated with a transaction. For example, in various embodiments, thetransaction information may include a price, credit card information,loyalty information, product information, store information, timeinformation, location information, discount information, method ofpurchase information, and/or any other type of transaction-relatedinformation.

Further, the indicia displayed for prompting user input to allow thetransaction to occur may include any type of indicia capable ofprompting the aforementioned user input. For example, in one embodiment,the indicia may include an accept icon. The accept icon may include anyicon indicating acceptance of the transaction. For example, in oneembodiment, the accept icon may include an icon with the word “Accept.”In another embodiment, the accept icon may include a thumbs-up icon. Inanother embodiment, the accept icon may include an “OK” indicator. Inanother embodiment, the accept icon may include a “YES” indicator. Inanother embodiment, the accept icon may include a “Purchase” indicator.In another embodiment, the accept icon may include a transaction priceindicator, capable of being selected to indicate acceptance. In anotherembodiment, the accept icon may include a button. In another embodiment,the accept icon may include a slider.

Additionally, in one embodiment, the indicia may include a passwordentry menu. For example, a keyboard may be presented to a user of themobile device, along with an entry portion. As an option, the passwordentry may be displayed in response to a slide gesture in connection witha slider icon.

In another embodiment, the indicia may include fingerprint scannerindicia. For example, in one embodiment, an indicator (and/or text) toscan a fingerprint may be displayed on the screen of the mobile device.In another embodiment, an area to scan a fingerprint may be displayed onat least a portion of a screen of the mobile device. In one embodiment,the user may be prompted to capture an image of a fingerprint, foranalysis.

In another embodiment, the indicia may include facial recognitionindicia. For example, in one embodiment, an indicator (and/or text) toscan or present a face may be displayed on the screen of the mobiledevice. In another embodiment, a button or icon to capture a face may bedisplayed on at least a portion of a screen of the mobile device.

In another embodiment, the indication may be capable of being receivedwhile a screen-lock graphical user interface is being displayed by themobile device. For example, in one embodiment, the user may be requiredto enter a password/passcode to access some or most functionallyassociated with the mobile device. In this case, in one embodiment, thescreen-lock graphical user interface may be displayed, and theindication may be capable of being received and/or the indicia may becapable of displayed on the screen-lock graphical user interface. In oneembodiment, the indicia may be capable of being displayed on a portionof the screen-lock graphical user interface (e.g. between an upper timeand/or date indicia and lower screen-lock graphical user interfacefunctionality in the form of a slider bar and/or password entryinterface, etc.).

In another embodiment, the indication may be capable of being receivedwhile the mobile device is in a standby mode. In one embodiment, thestandby mode may include displaying a standby screen on the mobiledevice. In another embodiment, the standby mode may include the display(e.g. backlight, etc.) of the mobile device being powered off. In thiscase, in one embodiment, the indication may cause the automatic poweringof the display screen (e.g. backlight, etc.), in addition to the displayof the indication. In such embodiment, after the display screen ispowered on, the indication may or may not be displayed in connectionwith a screen-lock graphical user interface (as set forth in theprevious embodiment).

In yet another embodiment, the indicia may be displayed utilizing atransaction application installed on the mobile device. For example, inone embodiment, a mobile wallet application may be installed on themobile device. In this case, in one embodiment, the mobile walletapplication or an application associated therewith may be utilized todisplay the indicia.

In another embodiment, the indicia may be displayed utilizing atransaction application installed on the mobile device, that isautomatically executed in immediate response to the receipt of anindication that the mobile device has established a first communicationwith the point-of-sale terminal via a first communication protocol otherthan a second communication protocol associated with the establishedcommunication that allows the transaction to occur. The communicationprotocols may include any type of protocol. For example, in oneembodiment, the first communication protocol may include a Wi-Fi orBluetooth communication protocol and the second communication protocolmay include a near field communication protocol. In another embodiment,the first communication protocol and/or the second communicationprotocol may include a cellular, Internet, Wi-Fi, Bluetooth, and/or anear field communication protocol.

In another embodiment, pre-transaction functionality may be provided bythe transaction application. In various embodiments, the pre-transactionfunctionality may include advertising, suggestion-related functionality,location-related functionality (e.g. store location relatedfunctionality, product-related functionality, etc.), point-of-saleterminal-related functionality, and/or loyalty-related functionality,etc. In one embodiment, the pre-transaction functionality may beutilized to initiate a transaction.

In one embodiment, it may be desired that the pre-transactionfunctionality occur before reaching a point-of-sale termination. Thus,in one possible embodiment, a service (administered, for example, by anapplication on the mobile phone and software at the point-of-saleterminal) may determine that a first dynamic location of the mobiledevice being within a predetermined distance (e.g. a few feet, yards,within a radius, within a building/retail location perimeter, etc.) of asecond predetermined location of the point-of-sale terminal. Upon suchdetermination, the service may send an indication signal to the mobiledevice (e.g. via the application) to initiate or otherwise cause thepre-transaction functionality.

Additionally, in one embodiment, the indication may be received based ona physical contact between the mobile device and the point-of-saleterminal. In one embodiment, the physical contact may include physicalcontact with a designated portion of the mobile device and/or thepoint-of-sale terminal. In another embodiment, the indication may bereceived based on close physical proximity between the mobile device andthe point-of-sale terminal. Further, in one embodiment, the physicalcontact may be detected utilizing bump technology.

The transaction information may be received from a variety of devices.For example, in one embodiment, the transaction information may bereceived by the mobile device from the point-of-sale terminal. Inanother embodiment, the transaction information may be received by themobile device from a network server. In another embodiment, thetransaction information may be received by the mobile device from apayment provider service or server.

In one embodiment, the transaction information may be displayedsimultaneously with the indicia. For example, in various embodiments, aprice, credit card information, and/or loyalty information may bedisplayed simultaneously with an accept icon, a password entry menu, afingerprint scanner indicia, and/or a facial recognition indicia.Further, in one embodiment, the indicia may be displayed utilizing atransaction application installed on the mobile device, which may beautomatically executed in immediate response to the receipt of theindication. In various embodiments, the transaction application mayinclude a mobile payment application, a mobile wallet application, acredit card application, and/or various other transaction-relatedapplications.

In another embodiment, the indicia may be displayed utilizing atransaction application installed on the mobile device that providespost-transaction functionality. In various embodiments, thepost-transaction functionality may include at least of advertising,loyalty-related functionality, return visit-related functionality,and/or suggestion-related information. Of course, embodiments arecontemplated whereby the post-transaction functionality is providedwithout a transaction application (e.g. via a web-service, browser,etc.).

The user input prompted by the indicia may include various user input.For example, in various embodiments, the user input that is prompted maybe in direct connection with the indicia (e.g. touch the icon displayedwith a touchscreen, etc.) and/or may be indirectly connected (e.g.indicia prompting user input via a mechanical button, voice input, etc.and/or other input not based on the touch screen, etc.). In oneembodiment, the indicia may instruct the user to provide a specificinput. For example, in one embodiment, the indicia may include textinstructions. Further, in various embodiments, the user input mayinclude a finger swipe, a finger depression, an image of the user (e.g.for the purposes of facial recognition, etc.), voice input, text input,and/or various other user input.

In one embodiment, the indicia may be displayed in immediate response tothe receipt of the indication, by displaying the indicia without anyintermediate graphical user interfaces. For example, in one embodiment,upon a mobile device establishing communication with the point-of-saleterminal, the indicia for prompting the user input may be automaticallyand immediately displayed on a screen of the mobile device. In oneembodiment, the indicia for prompting the user input may beautomatically and immediately displayed on a screen of the mobile deviceonly if a potential transaction is available (e.g. if there are item ina digital shopping cart, if there are items in a physical shopping cart,etc.).

Further, in one embodiment, the transaction may be immediately allowedto occur in response to the receipt of the user input. In oneembodiment, the transaction may be immediately allowed to occur inresponse to the receipt of the user input, by allowing the transactionto occur without any additional graphical user interfaces.

In one embodiment, the mobile device and/or the point-of-sale terminalmay include transaction-related functionality. In various embodiments,the transaction-related functionality may include pre-transactionfunctionality, a transaction, and/or post-transaction functionality. Itshould be noted that the aforementioned pre-transaction, transaction,and/or post-transaction functionality may or may not include any of thetechniques disclosed during the description of any of the figuresherein. Further, in one embodiment, the transaction-relatedfunctionality may be provided by a transaction application installed onthe mobile device.

Still yet, in one embodiment, the point-of-sale terminal may beassociated with (e.g. in communication with, etc.) one or more serviceproviders (e.g. advertisers, social network systems, retailers, etc.).Additionally, in one embodiment, the point-of-sale terminal and/or themobile device may be in communication with a system capable of storingprofile information associated with members of a service network,storing advertisement trigger information associated with advertisementsof an advertiser, and/or for causing presentation of at least one of theadvertisements outside of the service network, based on the profileinformation and the advertisement trigger information. Of course, anydescription herein of such presentation of one or more advertisementsoutside of the service network (and any related functionality disclosedherein) may be implemented without involving a point-of-sale terminal.

In various embodiments, the service network may include at least one ofa social network, an e-commerce network, an e-wallet network, or asearch network, etc. Further, the profile information may include anytype of profile information. For example, in one embodiment, the profileinformation may include interest information and/or demographicinformation.

Of course, in various embodiments, the profile information may includeany type of information, such as browsing history, social networkinformation, a gender, an age, a birth date, an astrological sign, anationality, a religion, a political affiliation (e.g. Democrat,Republican, etc.), a height, a weight, a hair color, an eye color, anethnicity, a living address (e.g. a home address, etc.), a work address,an occupation (e.g. student, engineer, barista, unemployed, etc.), asexual preference, an education level (e.g. a high school education, acollege education, a postgraduate degree, etc.), a birth place, a schoolattended (e.g. an elementary school attended, a middle school attended,a high school attended, a college attended, etc.), an area once lived(e.g. during adolescence, after high school, during adult years, etc.),a relationship status (e.g. single, married, significant other, etc.), afamily status (e.g. living parents, divorced parents, estranged fromparents, etc.), a number of siblings, an income level, a car status(e.g. a car model, a car make, a car year, a car price, etc.), a numberof children, hobbies (e.g. reading, running, volunteering, biking, golf,climbing, etc.), exercise habits (e.g. number of hours/minutes a week,number of times a month, type of exercise preferred, etc.), a number ofpets owned, a type of pets owned (e.g. dogs, cats, fish, gerbils, etc.),food preferences (e.g. vegetarian, vegan, mainly meat, Chinese cuisine,Mexican cuisine, etc.), drinking habits (e.g. daily, weekly, monthly,etc.), eating habits (e.g. eat in, dine out, snacks, meals, etc.), TVwatching preferences (e.g. types of preferred shows, number ofhours/minutes per day/week, etc.), movie watching preferences (e.g.types of preferred movies, number of movies per day/week/month, etc.),music preferences (e.g. preferred genre, preferred artist, etc.),sleeping preferences (e.g. the number of hours of sleep preferred, thepreferred bed time/rise time, etc.), moods (e.g. generally a good mood,generally a bad mood, etc.), feelings (e.g. generally happy, generallysad, generally angry, etc.), desires (e.g. goals, wishes, etc.), and/orany other personal information.

In various embodiments, the personal information may include permanentpersonal information (e.g. physical traits, history, etc.), temporalpersonal information (e.g. what the user is doing/feeling/experiencingnow or within a predetermined window of time, etc.), and/or futuregoal-oriented personal information (e.g. wants, desires, etc.).

In one optional embodiment, the personal information may be received inassociation with a social networking site that allows users to definethemselves in a profile (e.g. which may include any one or more of thepersonal information parameters disclosed hereinabove and/or hereinbelow, etc.); associate themselves with others (e.g. friends,colleagues, other groups, etc.) by connecting to each other; and/orengage in activities (e.g. using applications such as games, reviewingcontent, sharing content (e.g. interests, thoughts, questions, media,etc.), etc.

In such embodiment, the personal information may be received from asocial networking profile of the user associated with a socialnetworking site. Further, the personal information may include anyentities (e.g. people, groups, institutions, products, etc.) to whichthe user is associated (e.g. connected, subscribed, linked) during useof the social networking site. Such associations may also be extended to“associations-of-associations” (e.g. friends of friends, etc.). Evenstill, tracking such associations as personal information may beextended to a threshold number (e.g. 1, 2, 3, 4, 5, etc.) ofdegrees-of-separation. As a further option, the personal information maybe received based on any of the aforementioned activity of the user inconnection with the social networking site. In such example, anyprofiling metadata collected based on the activity of the user may beutilized as the personal information.

One optional embodiment is contemplated wherein an on-line applicationassociated with the social networking site may collect and/or use theaforementioned social networking site-related personal information inconnection with any of the functionality disclosed hereinabove and/orherein below. Of course, such social networking site-related on-lineapplication may do so by itself and/or in connection with other one ormore social networking site-related on-line application(s) orseparate/independent site-related on-line application(s).

In one embodiment, a pre-existing social networking site may beleveraged to accomplish any one or more of the operations disclosedherein. With that said, any site that collects any of the personalinformation disclosed herein may optionally be used in lieu of or incombination with the aforementioned social networking site. For example,an e-commerce site (e.g. product supply website, etc.) that collectsprofile information, etc. may be utilized in a similar manner.

More information regarding leveraging service providers to collectinformation may be found in U.S. Provisional Patent Application No.61/563,741, filed Nov. 25, 2011, titled “SYSTEM, METHOD, AND COMPUTERPROGRAM PRODUCT FOR PRESENTING DECISION RELATED INFORMATION;” and U.S.Provisional Patent Application No. 61/590,764, filed Jan. 25, 2012,titled “SYSTEM, METHOD, AND COMPUTER PROGRAM PRODUCT FOR PRESENTINGINFORMATION TO A USER BASED ON DETERMINED SATISFACTION-RELATEDINFORMATION ASSOCIATED WITH THE USER,” which are incorporated herein byreference in their entirety.

Further, in one embodiment, targeted advertisements may be presented tothe user on the mobile device, based on any user information. In oneembodiment, the advertisement may be presented outside of the servicenetwork. In this case, in one embodiment, the presentation of theadvertisement outside of the service network may be accomplished by theservice network transmitting a signal outside the service network.

Further, in one embodiment, the signal may be time-stamped.Additionally, in one embodiment, the presentation of the at least oneadvertisement outside of the service network may be accomplished by theservice network transmitting the advertisement outside the servicenetwork. In one embodiment, a format of the advertisement may be basedon presentation medium specification information. For example, in oneembodiment, the advertisement may be formatted to present on the mobiledevice. In another embodiment, the advertisement may be formatted to bepresented on a display associated with the point-of-sale terminal. Inanother embodiment, the advertisement may be formatted to be displayedon a billboard and/or an in store display. In still another embodiment,the advertisement may be displayed via a television.

Additionally, in one embodiment, the at least one advertisement may betime-stamped. In one embodiment, the time stamp me be utilized todetermine a duration in which the advertisement is to be displayed. Inanother embodiment, the time stamp may be utilized to determine a timein which the advertisement is to expire.

Further, in one embodiment, the advertisement may be presented via aserver in communication with a plurality of presentation mediums, wherethe server is operable to cooperate with the server network. In anotherembodiment, the advertisement may be presented via at least one of aplurality of presentation mediums each with client code operable tocooperate with the server network. In various embodiments, theadvertisement may be presented by the advertiser or a party separatefrom the service network and the advertiser.

Additionally, in one embodiment, the advertisement may be presentedbased on location information associated with members of the servicenetwork. In one embodiment, the location information may be determinedby the service network. In various embodiments, the location informationmay be determined utilizing GPS, Wi-Fi, an IP address, and/or variousother techniques (e.g. manual indication by the member(s), etc.).Furthermore, in various embodiments, the service network may include anynumber of service networks, such as a social network, an e-commercenetwork, an e-wallet network, and/or a search network, etc.

More illustrative information will now be set forth regarding variousoptional architectures and features with which the foregoing techniquesdiscussed in the context of any of the present or previous figure(s) mayor may not be implemented, per the desires of the user. For instance,various optional examples and/or options associated with thecommunication/indication of operation 302, the transaction/indicia ofoperation 304, and/or other optional features have been and will be setforth in the context of a variety of possible embodiments. It should bestrongly noted, however, that such information is set forth forillustrative purposes and should not be construed as limiting in anymanner. Any of such features may be optionally incorporated with orwithout the inclusion of other features described.

FIG. 4 shows a system 400 for mobile device transactions, in accordancewith another embodiment. As an option, the system 400 may be implementedin the context of the architecture and environment of the previousFigures and/or any subsequent Figure(s). Of course, however, the system400 may be implemented in the context of any desired environment. Itshould also be noted that the aforementioned definitions may applyduring the present description.

As shown, a service network system may include a database 402 and server404. The service network system may be associated with a variety ofservice networks, including a social network, a retailer, a paymentprovider, payment facilitator, an advertiser, a search engine system, amobile wallet system, a media provider, and/or any other service networksystem that provides one or more services to its members.

The service network system may be in communication with one or morethird party systems. For example, in one embodiment, the service networksystem may be in communication with a third party retailer, advertiser,and/or payment system that each include one or more third partyserver(s) 406. Additionally, in one embodiment, the service networksystem may be in communication with one or more third party clientdevices 412-416. In various embodiments, the client devices may includemobile phones, computers, media devices, displays, payment systems,point-of-sale terminals, and/or various other devices.

In another embodiment, the devices 408-418 may include a vehicularhead-unit display associated with a vehicular assembly. One example ofsuch a vehicular assembly may include that which is disclosed in U.S.Pat. No. 8,131,458 issued Mar. 6, 2012 and entitled “SYSTEM, METHOD, ANDCOMPUTER PROGRAM PRODUCT FOR INSTANT MESSAGING UTILIZING A VEHICULARASSEMBLY,” which is incorporated herein by reference in its entirety. Inthe present embodiment, such head-unit display may communicate with theservers 404 and/or 406 via a communication channel of a mobile device(as taught in U.S. Pat. No. 8,131,458). Of course, in other embodiments,the vehicle (and thus the head-unit display) may be equipped with itsown modem for communicating directly with the servers 404 and/or 406.

In different embodiments, the displays 408-416 may or may not beequipped with software (e.g. a plug-in and/or an application program,etc.) for providing an interface to receive/send signals with respect tothe server 406 and/or 404. Such software may also include interface code(e.g. driver, etc.) for accommodating the specific protocol/format, etc.of the displays 408-416 and otherwise controlling the same (and contentdisplayed). In other embodiments, of course, the signals/controladministered by the server 406 and/or 404 may be standardized such thatcommunications may be directed at the displays 408-416 without the needfor additional software.

Furthermore, in one embodiment, the service network system may be incommunication with systems/displays dedicated (at least in part) todisplaying advertisements, deals, and/or for facilitating payment ofproducts and/or services. For example, in one embodiment, the servicenetwork system may be in communication with a third party server 406and/or one or more location specific displays 408-410.

In the context of the present description, a location specific displayrefers to a display associated with a location. For example, in variousembodiments, the location specific display may include a display at abusiness location (e.g. a monitor, a television, a computer display,etc.), a billboard, a display associated with a point-of-sale terminal,a display associated with a product/service (e.g. a display at a gaspump, etc.), and/or any other type of display.

The communication between the service network system and the third partysystem may be facilitated utilizing a variety of techniques. Forexample, in one embodiment, the communication between the servicenetwork system and the third party system may include directcommunication (e.g. a wireless direct connection, a wired directconnection, etc.). In another embodiment, the communication between theservice network system and the third party system may include indirectcommunication (e.g. communication via a server, communication via acloud, communication via one or more other systems, etc.).

In operation, in one embodiment, the service network may be operable tocause the display of targeted advertisements and/or targeted content onthe location specific displays 408-410 and/or the client devices412-416. In one embodiment, the service network system may push theadvertisements (e.g. including advertisement content, etc.) to thelocation specific displays 408-410 and/or the client devices 412-416. Inanother embodiment, the service network system may push an advertisementtrigger ID to another system (e.g. the server 406, etc.) such that theadvertisements are displayed on the location specific displays 408-410and/or the client devices 412-416. Of course, in some embodiments, theaforementioned advertisement trigger ID may be sent directly to thelocation specific displays 408-410 and/or the client devices 412-416,for using the same to access appropriate advertisements locally and/orremotely.

For example, in one embodiment, it may be determined that a user is inthe vicinity of the one or more location specific displays 408-410.Accordingly, in one embodiment, targeted content and/or advertisementsmay be presented to the user on the one or more location specificdisplays 408-410. In one embodiment, the targeted content and/oradvertisements presented to the user on the one or more locationspecific displays 408-410 may include targeted content and/oradvertisements associated with the location.

The location of the user may be determined utilizing a variety oftechniques. For example, in one embodiment, the user may digitally checkin to a location. In various embodiments, the user may check-in to thelocation utilizing a mobile device associated with the user, a systemassociated with the location, and/or another device. In one embodiment,the user may check in to a location utilizing an application stored onthe mobile device of the user. In various embodiments, the applicationmay include a social network application, an application associated withthe location, a mapping application, a geo-caching application, a mobilepayment application, and/or various other applications. In anotherembodiment, the user may check in to a location utilizing a check-insystem associated with the location.

In another embodiment, a mobile device of the user may be utilized toautomatically check in to a location. For example, in one embodiment, anapplication stored on the mobile device may be utilized to automaticallycheck in to a location (e.g. based on a wireless signal, based on awireless network availability, based on GPS, a bump signal, an NFCsignal, etc.).

More information regarding checking in to a location, etc. may be foundin U.S. Provisional Patent Application No. 61/590,767, filed Jan. 25,2012, titled “SYSTEM, METHOD AND COMPUTER PROGRAM PRODUCT FORLOCATION-SPECIFIC PRIVACY SETTINGS;” U.S. Provisional Patent ApplicationNo. 61/591,819, filed Jan. 27, 2012, titled “SYSTEM, METHOD, ANDCOMPUTER PROGRAM PRODUCT FOR ALTERING AT LEAST ONE ASPECT OF ANINTEGRATED E-COMMERCE ON-LINE APPLICATION;” and U.S. Provisional PatentApplication No. 61/596,174, filed Feb. 7, 2012, titled “SYSTEM, METHOD,AND COMPUTER PROGRAM PRODUCT FOR ALTERING AT LEAST ONE ASPECT OF ANINTEGRATED E-COMMERCE ON-LINE APPLICATION,” which are each incorporatedherein by reference in their entirety.

Further, in one embodiment, the location of the user may be determinedbased on GPS. For example, the mobile device (and/or an application/OSassociated therewith) may share GPS data associated with the mobiledevice, such that the location of the mobile device/user is determined.In one embodiment, the GPS data may be shared with the service networksystem. In another embodiment, the GPS data may be shared with one ormore third party systems.

In another embodiment, the location of the user may be determined basedon a signal provided by the mobile device of the user. For example, inone embodiment, the mobile device of the user may provide a Bluetoothsignal that is capable of being received by a device associated with thelocation (e.g. a display, a computer, a location detection device, apoint-of-sale device, etc.), such that location may be determined. Inanother embodiment, the mobile device of the user may provide a NFCsignal that is capable of being received by a device associated with thelocation (e.g. a display, a computer, a location detection device, apoint-of-sale device, etc.), such that location may be determined.

In another embodiment, the mobile device of the user may provide a Wi-Fisignal that is capable of being received by a device associated with thelocation (e.g. a router, a display, a computer, a location detectiondevice, a point-of-sale device, etc.), such that location may bedetermined. In another embodiment, the mobile device of the user mayprovide a chirp signal that is capable of being received by a deviceassociated with the location, such that location may be determined. Inone embodiment, the chirp signal may include information associated withthe location (e.g. GPS coordinates, etc.). In one embodiment, a signalstrength associated with the chirp may be used to associate the userwith a location.

In another embodiment, the mobile device may be connected to a wirelessnetwork associated with the location automatically (or manually), suchthat a location may be determined. In still another embodiment, thelocation of the user may be determined utilizing facial recognitiontechniques. For example, in one embodiment, a system associated with thelocation may be utilized to determine the user is present based onfacial recognition.

More information regarding facial recognition and other features thatmay or may not be incorporated into any of the embodiments disclosedherein, may be found in U.S. patent application Ser. No. 13/652,458,filed Oct. 15, 2012, titled “MOBILE DEVICE SYSTEM, METHOD, AND COMPUTERPROGRAM PRODUCT,” which is incorporated herein by reference in itsentirety.

In another embodiment, the location of the user may be determinedutilizing social network status associated with the user. Optionally,such social network status may be set by another person (e.g. friend,etc. of the user, etc.). This may be accomplished by “tagging” the userin association with a particular location (e.g. by naming the locationor tagging the user in association with a location associated with thefriend, etc.).

In another embodiment, the location of the user may be determined basedon an action of the user. For example, in one embodiment, the user mayutilize the mobile device to scan a bar code of an item (e.g. a product,a poster, a billboard, etc.), such that the location of the user may bedetermined. In another embodiment, the user may utilize the mobiledevice to capture an image of an item (e.g. a building, a sign, aproduct, a poster, a billboard, etc.), such that the location of theuser may be determined.

In another embodiment, the location of the user may be determined and/orthe aforementioned/following determination techniques may be confirmedby an interaction of the user with the display. As an option, suchinteraction may include detecting a touch or gesture (or other input) bythe user of a touchscreen associated with the display (408-416) and/or aseparate control display/controller associated with the display(408-416).

In another embodiment, the user may utilize the mobile device tofacilitate a purchase at a location (e.g. utilizing an e-walletapplication, utilizing a digital credit card, utilizing a digital debitcard etc.), such that the location of the user may be determined. Inanother embodiment, the user may utilize a payment techniqueattributable to the user to facilitate a purchase at a location (e.g.utilizing gift card, utilizing a credit card, utilizing a debit cardetc.), such that the location of the user may be determined. In anotherembodiment, the user may scan a loyalty card at a location, such thatthe location of the user may be determined. Of course, any technique maybe utilized to determine a location associated with the user.

Once the location of the user is determined, in one embodiment, it mayor may not be determined whether the user is in the vicinity of adisplay capable of displaying targeted advertisements/content. In oneembodiment, the location specific display (or a system associatedtherewith) may determine the user is in the vicinity (e.g. utilizing oneof the various location determination techniques described, etc.). Inanother embodiment, the location of the location specific displays maybe known. For example, in one embodiment, the location specific displaysmay be registered and the location may be logged (e.g. utilizing thedatabase 402, the server 404, another database or server, etc.).

If the location of the location specific display is known, and thelocation of the user is known (at least to within a threshold distance,etc.), targeted advertisements/content may be displayed to the user onthe location specific displays 408-410 and/or on the client devices412-416, based on the location of the user. As an example, the user mayutilize the client device 412 (e.g. a point-of-sale terminal, etc.) toinitiate a purchase of products. Accordingly, the location of the userand the client device 412 are determined and targetedadvertisements/content may be presented to the user on a displayassociated with the client device 412.

As another example, the location of the user may be determined (e.g.utilizing one or more of the location determination techniques describedabove, etc.) and it may be determined that the user is in the vicinityof a known location specific display 408. Accordingly, targetedadvertisements/content may be presented to the user on the locationspecific display 408.

As yet another example, the location specific display may determine thatthe user is in the vicinity (e.g. utilizing one or more of the locationdetermination techniques described above, etc.). Accordingly, targetedadvertisements/content may be presented to the user on the locationspecific display 408. In one embodiment, the targetedadvertisements/content may be pushed from the service network systemserver 404 (e.g. to the location specific displays 408-410 and/or theclient devices 412-416, etc.). In another embodiment, the targetedadvertisements/content may be pushed from the third party system server406 (e.g. to the location specific displays 408-410 and/or the clientdevices 412-416, etc.).

The targeted advertisements/content may be determined utilizing avariety of criteria associated with the user and/or the location. Forexample, in one embodiment, social network information may be utilizedto determine targeted advertisements/content. In another embodiment,online retailer information may be utilized to determine targetedadvertisements/content.

In another embodiment, previous purchase information may be utilized todetermine targeted advertisements/content. In another embodiment, mobilewallet application information may be utilized determine targetedadvertisements/content. In another embodiment, loyalty information maybe utilized determine targeted advertisements/content. In anotherembodiment, personal information may be utilized determine targetedadvertisements/content.

More information regarding targeted advertisements/content and theinformation utilized to determine such advertisements/content may befound in U.S. Provisional Patent Application No. 61/563,741, filed Nov.25, 2011, titled “SYSTEM, METHOD, AND COMPUTER PROGRAM PRODUCT FORPRESENTING DECISION RELATED INFORMATION;” and U.S. Provisional PatentApplication No. 61/590,764, filed Jan. 25, 2012, titled “SYSTEM, METHOD,AND COMPUTER PROGRAM PRODUCT FOR PRESENTING INFORMATION TO A USER BASEDON DETERMINED SATISFACTION-RELATED INFORMATION ASSOCIATED WITH THEUSER,” which are incorporated herein by reference in their entirety.

In various embodiments, the personal information may include any type ofinformation, such as browsing history, social network information, agender, an age, a birth date, an astrological sign, a nationality, areligion, a political affiliation (e.g. Democrat, Republican, etc.), aheight, a weight, a hair color, an eye color, an ethnicity, a livingaddress (e.g. a home address, etc.), a work address, an occupation (e.g.student, engineer, barista, unemployed, etc.), a sexual preference, aneducation level (e.g. a high school education, a college education, apostgraduate degree, etc.), a birth place, a school attended (e.g. anelementary school attended, a middle school attended, a high schoolattended, a college attended, etc.), an area once lived (e.g. duringadolescence, after high school, during adult years, etc.), arelationship status (e.g. single, married, significant other, etc.), afamily status (e.g. living parents, divorced parents, estranged fromparents, etc.), a number of siblings, an income level, a car status(e.g. a car model, a car make, a car year, a car price, etc.), a numberof children, hobbies (e.g. reading, running, volunteering, biking, golf,climbing, etc.), exercise habits (e.g. number of hours/minutes a week,number of times a month, type of exercise preferred, etc.), a number ofpets owned, a type of pets owned (e.g. dogs, cats, fish, gerbils, etc.),food preferences (e.g. vegetarian, vegan, mainly meat, Chinese cuisine,Mexican cuisine, etc.), drinking habits (e.g. daily, weekly, monthly,etc.), eating habits (e.g. eat in, dine out, snacks, meals, etc.), TVwatching preferences (e.g. types of preferred shows, number ofhours/minutes per day/week, etc.), movie watching preferences (e.g.types of preferred movies, number of movies per day/week/month, etc.),music preferences (e.g. preferred genre, preferred artist, etc.),sleeping preferences (e.g. the number of hours of sleep preferred, thepreferred bed time/rise time, etc.), moods (e.g. generally a good mood,generally a bad mood, etc.), feelings (e.g. generally happy, generallysad, generally angry, etc.), desires (e.g. goals, wishes, etc.), and/orany other personal information.

In various embodiments, the personal information may include permanentpersonal information (e.g. physical traits, history, etc.), temporalpersonal information (e.g. what the user is doing/feeling/experiencingnow or within a predetermined window of time, etc.), and/or futuregoal-oriented personal information (e.g. wants, desires, etc.).

Further, in one embodiment, the personal information may be received inassociation with a social networking site that allows users to definethemselves in a profile (e.g. which may include any one or more of thepersonal information parameters disclosed hereinabove and/or hereinbelow, etc.); associate themselves with others (e.g. friends,colleagues, other groups, etc.) by connecting to each other; and/orengage in activities (e.g. using applications such as games, reviewingcontent, sharing content (e.g. interests, thoughts, questions, media,etc.), etc. In such embodiment, the personal information may be receivedfrom a social networking profile of the user associated with a socialnetworking site. Further, the personal information may include anyentities (e.g. people, groups, institutions, products, etc.) to whichthe user is associated (e.g. connected, subscribed, linked) during useof the social networking site. Such associations may also be extended to“associations-of-associations” (e.g. friends of friends, etc.). Evenstill, tracking such associations as personal information may beextended to a threshold number (e.g. 1, 2, 3, 4, 5, etc.) ofdegrees-of-separation. As a further option, the personal information maybe received based on any of the aforementioned activity of the user inconnection with the social networking site. In such example, anyprofiling metadata collected based on the activity of the user may beutilized as the personal information.

One optional embodiment is contemplated wherein an on-line applicationassociated with the social networking site may collect and/or use theaforementioned social networking site-related personal information inconnection with any of the functionality disclosed hereinabove and/orherein below. Of course, such social networking site-related on-lineapplication may do so by itself and/or in connection with other one ormore social networking site-related on-line application(s) orseparate/independent site-related on-line application(s).

Still yet, in one embodiment, the database 402 may include loyalty cardinformation. In various embodiments, such loyalty card information mayinclude types of products purchased, frequency that products arepurchased, brands of products purchased, number of days/hours shoppingper week/month, amount of money spent (e.g. average amount per outing,average amount per month, average amount per week, least amount perouting, etc.), discount amount (e.g. average amount per outing, averageamount per month, average amount per week, least amount per outing,etc.), awards points, and/or various other information.

Furthermore, in one embodiment, the database 402 may store locationbased information. For example, in various embodiments, the database 402may store information associated with product offerings associated witha location, store options associated with a location, service optionsassociated with a location, advertisements associated with a location,maps associated with the location, and/or various other information.

Further, in one embodiment, the database 402 may store business relatedinformation. For example, in various embodiments, the business relatedinformation may include business location information, businessoperation information, business hours, business specials, businessofferings, business deals, and/or various other business relatedinformation. Additionally, in one embodiment, the database 402 mayinclude targeted content/advertisement information (e.g. advertisementIDs, advertisements, advertisement trigger IDs, etc.).

In various embodiments, any information stored in the database 402 (orany other accessible database, etc.) may be utilized to determineadvertisements/content to present to a user. Of course, in oneembodiment, the information stored in the database 402 (or any otheraccessible database, etc.) may be associated with individual usersand/or groups of users.

As one exemplary implementation associated with one embodiment, a usermay be shopping in a market. Utilizing one or more locationdetermination techniques discussed above, the location of the user maybe determined and a display that is capable of being viewed by the usermay be determined. In one embodiment, information associated with theuser may be utilized to determine an advertisement/content to bepresented to the user on the display. In one embodiment, the server 404may determine the advertisement/content to display, based on theinformation. In another embodiment, the server 406 may determine theadvertisement/content to display, based on the information. In anotherembodiment, at least one of the client devices 412-416 may determine theadvertisement/content to display.

Further, in various embodiments, the server 404 and/or the server 406may send the targeted advertisements/content and/oradvertisement/content trigger IDs. In the case that the server 404and/or the server 406 sends advertisement/content trigger IDs, thereceiving apparatus or system (e.g. the client devices 412-416, theserver 406, the location specific displays 408-410, etc.) may utilizethe advertisement/content trigger IDs to select and display theadvertisement/content. In one embodiment, each advertisement/content orgroup of advertisements/content may be associated with at least oneadvertisement/content trigger ID, such that the advertisement/contenttrigger ID may be utilized to look up associated advertisement/content.In various embodiments, the advertisement/content trigger IDs mayinclude numerical IDs, alpha-numeric IDs, key word IDs, and/or variousother IDs. In one embodiment, the third party system may include its ownadvertisement/content database, where advertisements/content may beaccessed.

As another exemplary implementation, a user may be shopping and initiatea checkout/payment utilizing a point-of-sale terminal (e.g. one or moreof the client devices 412-416, etc.). In various embodiments, the usermay initiate payment utilizing a mobile phone (e.g. in association withan e-wallet application, a credit card application, etc.), a creditcard, a loyalty card, a loyalty card and cash, a check, and/or variousother techniques. Utilizing loyalty card information, mobile deviceinformation, payment information, and/or various other information, theuser identification may be determined (and/or information associatedwith the user, which is capable of being utilized to determined targetedadvertisements/content may be determined, etc.). Because the user ischecking out at a known location, advertisements/content may be selectedfor the user (based on known or determined information about the user,etc.) and one or more advertisements/content may be displayed on adisplay associated with the point-of-sale terminal (and/or a display inproximity to the point-of-sale terminal, on a mobile device of the user,etc.).

The content/advertisements may include any type of content and/oradvertisements. For example, in various embodiments, thecontent/advertisements may include product/service suggestions based onuser purchase history, product/service suggestions based on itemsomitted during checkout, product/service suggestions based on itemspurchased, product/service suggestions based on location,product/service suggestions based on amount of money spent on particularproducts/services (e.g. per week, per month, per shopping experience,etc.), product/service suggestions based on a demographic categoryassociated with the user, product/service suggestions based on userpersonal information, and/or any other type of content/advertisement.

Furthermore, the advertisement/content presentation may be triggered ina variety of ways. For example, in one embodiment, theadvertisement/content presentation may be triggered upon initiation ofcheck-out (e.g. upon scanning a loyalty card, upon scanning a firstitem, etc.). In another embodiment, the advertisement/contentpresentation may be triggered upon initiation of payment. In anotherembodiment, the advertisement/content presentation may be triggered uponapproval of payment. In another embodiment, the advertisement/contentpresentation may be triggered upon a determination of a location of theuser.

In another embodiment, the advertisement/content presentation may betriggered utilizing a signal associated with the mobile device (e.g. anNFC signal, a Bluetooth signal, a Wi-Fi direct signal, etc.). In anotherembodiment, the advertisement/content presentation may be triggeredbased on a facial recognition program identifying the user. In anotherembodiment, the advertisement/content presentation may be triggered upona user check-in (e.g. a manual check-in, an automatic check-in, etc.).

In another embodiment, the advertisement/content presentation may betriggered when a user scans an item utilizing the mobile device. Forexample, in one embodiment, the user may scan a barcode of an itemutilizing the mobile device and an advertisement/content may bepresented to the user on a display of the mobile device and/or onanother display (e.g. a display determined to be in the vicinity of theuser, etc.). In another embodiment, the user may capture an image of anitem and an advertisement/content may be presented to the user on adisplay of the mobile device and/or on another display (e.g. a displaydetermined to be in the vicinity of the user, etc.).

In another embodiment, the advertisement/content presentation may betriggered in response to a user request. For example, in one embodiment,a user may utilize an associated mobile device to view availableadvertisements/content and/or to request targetedadvertisements/content. In this case, in various embodiments, theadvertisements/content may be displayed on a display associated with themobile device and/or another display.

In one embodiment, the advertisement/content may be displayed in anon-intrusive manner on the mobile device display. For example, in oneembodiment, the advertisement/content may be displayed on a lock screenof the mobile device. In another embodiment, the advertisement/contentmay be displayed utilizing a specific advertisement/content displayapplication.

More information about non-intrusively displaying advertisements on amobile device may be found in U.S. Provisional Patent Application No.61/711,727, filed Oct. 9, 2012, titled “SYSTEM, METHOD, AND COMPUTERPROGRAM PRODUCT FOR DETERMINING WHETHER TO PROMPT AN ACTION BY APLATFORM IN CONNECTION WITH A MOBILE DEVICE,” which is incorporatedherein by reference in its entirety.

Further, in one embodiment, an advertisement/content may be displayed ona display separate from a mobile device and the user may have the optionto transfer display of the advertisement/content to the mobile device,or to receive the advertisement/content on the mobile device. Forexample, in one embodiment, an application on the mobile device maypresent the user an option to display an advertisement/content on themobile device, which is currently being displayed on a third partydisplay. In another embodiment, bump technology may be utilized totransfer an advertisement/content to the mobile device. For example, inone embodiment, advertisement/content may be displayed on a third partydisplay and a user may touch the display (or an interface associatedwith the display, etc.) such that the advertisement/content istransferred to the mobile device for display. Of course, in variousembodiments, various techniques may be utilized to transfer theadvertisement/content to the mobile device.

It should be noted that, although the apparatuses/systems/devicesillustrated in FIG. 4 are described in the context of individualdevices, in other embodiments, such apparatuses/systems/devices may becombined or implemented across multiple devices. For example, in oneembodiment, the database 402 may include a plurality of databases (e.g.controlled by different entities, etc.). In another embodiment, theserver 404 may represent a plurality of servers (e.g. controlled bydifferent entities, etc.). Furthermore, in one embodiment, multipleservice network systems and/or multiple third party systems maycommunicate with one another. For example, in one embodiment, a socialnetwork system and a mobile wallet system may be in communication andboth systems may be capable of communicating with one or more retailersand/or one or more service providers, etc.

To this end, in some embodiments, advertisements (and/or other content)may be displayed to a user in an intelligent manner; without having tonecessarily utilize precious interface “real-estate” (i.e. area, etc.)of the mobile device and/or of one particular application (e.g.associated with the service network, etc.,) on a mobile device; and/orwhen the mobile device and/or application is not even being utilized(e.g. viewed, etc.) during a relevant time for the advertisement/contentto be displayed, etc. Further, as an option, this may be accomplished bygoing beyond allowing third parties to associate advertisements withcertain profile criteria, for triggering the display of suchadvertisements in connection with service network content on a servicenetwork interface (via a service network application, etc.).Specifically, advertisements/triggers may be associated with certainprofile criteria (which may or may not be the same used above), so that,instead of the aforementioned display of the advertisements inconnection with service network content, triggers and/or theadvertisements are ultimately pushed to a separate display (e.g.408-416, etc.) or a separate context (e.g. different application, etc.)on the same display/device, for presentation.

Further, the various features disclosed herein may, in some optionalembodiments, be accomplished by both the service network and advertisertracking, storing, sharing, etc. at least one aspect of the user foruniquely or non-uniquely identifying the same, which may be done in ananonymous or non-anonymous manner. In various embodiments, such useridentifying aspect may take the form of data that includes and/or isbased, at least in part, on service network and/or advertiser usernameand/or password, a name, an alias, a user ID, a user email address, auser residence or business physical address, a user phone (e.g. cell)number, an application identifier, a user context identifier, a cookie,a session identifier, a purchase receipt reflecting a purchase by theuser, a credit card/bank account number and/or alias, a randomlygenerated identifier, a comment/posting, text/e-mail content, a facialrecognition result, a fingerprint scan result, an Internet search query,a photo taken by and/or including the user, a scan of a code (QuickResponse Code), an automatically (GPS, WiFi, etc.) generated location, amanual or automatically generated check-in status (e.g. with precisetime-stamped location), a bump technology transaction/signal, any uniqueor semi-unique identifier, etc.). In one embodiment, the useridentifying aspect(s) may include any of the location triggers set forthin the context of the description of operation 1102 of FIG. 11, to beset forth hereinafter in greater detail. In various embodiments, theabove user identifying aspect(s) may be sourced from the service network(and/or related application), the advertiser, an operating system of themobile device and/or any other source.

In use, in accordance with one possible embodiment, the aforementioneduser identifying aspect may be submitted with, linked to, and/orotherwise associated with a profile-related query that is defined by theadvertiser. To this end, the profile criteria associated with variouspreconfigured advertisements of the advertiser may be compared againstthe appropriate profile (and content) of the correct/relevant user inthe service network database (that is identified by the identifyingaspect), to be the subject of presentation of the advertisement.

In various embodiments, the aforementioned user identifying aspect maybe encrypted for ensuring anonymity of the user. More informationregarding various possible features and/or utilization of theaforementioned user identifying aspect may be found in U.S. ProvisionalPatent Application No. 61/563,741, filed Nov. 25, 2011, titled “SYSTEM,METHOD, AND COMPUTER PROGRAM PRODUCT FOR PRESENTING DECISION RELATEDINFORMATION;” and U.S. Provisional Patent Application No. 61/590,764,filed Jan. 25, 2012, titled “SYSTEM, METHOD, AND COMPUTER PROGRAMPRODUCT FOR PRESENTING INFORMATION TO A USER BASED ON DETERMINEDSATISFACTION-RELATED INFORMATION ASSOCIATED WITH THE USER,” which areincorporated herein by reference in their entirety.

Of course, embodiments are contemplated where the advertisements mayalso be triggered for display in a manner that utilizes the servicenetwork interface(s) and is integrated with service network content(e.g. “on-platform”) vs. the aforementioned “off-platform” advertising.In such other embodiments, the on- and off-platform advertising may becoordinated for increased effectiveness. For example, after the displayof an off-platform advertisement and in response to user input receivedin connection with such off-platform advertisement, an additionalescalation of advertising may be accomplished by displaying arelated/follow-up/supplemental on-platform advertisement. Of course,pricing of the related/follow-up/supplemental on-platform advertisementmay be varied (e.g. increased, etc.) to reflect the effectiveness ofsuch sequential targeted advertisements across multiple platforms. Stillyet, off-platform advertisements may be bid upon, since there often is asingle advertisement impression opportunity in connection with the useras he/she passes from location/context to location/context.

Even still, the service network may also establish policies to regulatethe issues that may arise when providing on- and off-platformadvertisements. Just by way of example, the service network may precludethe triggering of both an on- and off-platform advertisement to the sameperson at the same time.

In still other embodiments, the off-service network platformadvertisements may be displayed in connection with an application thatis initiated, accessible, etc. via an application associated with theservice network. As an option, any enabling off-platform advertisementtechniques (e.g. sharing of user information) and/or the display ofoff-platform advertisements themselves may be conditioned on the userauthorizing the same. For that matter, any technique disclosed hereinmay be subject to such user authorization.

FIG. 5 shows a system 500 for presenting advertisements/content, inaccordance with another embodiment. As an option, the system 500 may beimplemented in the context of the architecture and environment of theprevious Figures and/or any subsequent Figure(s). Of course, however,the system 500 may be implemented in the context of any desiredenvironment. It should also be noted that the aforementioned definitionsmay apply during the present description.

As shown, a social network system may be in communication with one ormore third party systems. In one embodiment, the social network systemmay include service functionality 502 that is in communication with oneor more databases 504. It should be strongly noted that, while a socialnetwork system is provided in the present embodiment, any servicenetwork system may be substituted therewith.

The social networking service functionality may include any onlineservice, platform, or site the helps facilitate the building of socialnetworks or social relations among people, groups, and/or businesses,etc., who, for example, share interests, activities, backgrounds, orreal-life connections. In various embodiments, the social networkservice may include a representation of each user (e.g. a profile,etc.), social link information, and a variety of additional services. Inone embodiment, the social network service may be web-based and mayallow for users to interact over the Internet, such as e-mail andinstant messaging.

In one embodiment, the social network service functionality may allow aprofile to be generated from a user answering to questions, such as age,location, interests, etc. In one embodiment, the social networkingservice functionality may allow the upload of pictures, multimediacontent, and/or modification of the look and feel of the profile.Further, in one embodiment, the social network service functionality mayallow users to enhance their profile by adding modules or applications.

In one embodiment, the social network service functionality may allowusers to post blog entries, search for others with similar interests,and compile and share lists of contacts. Additionally, in oneembodiment, the user profiles may have a section dedicated to commentsfrom friends and other users. Further, in one embodiment, to protectuser privacy, the social network service functionality may offercontrols that allow users to choose who can view their profile, contactthem, add them to their list of contacts, etc.

In another embodiment, the social network service functionality mayallow the user to create groups that share common interests oraffiliations, upload or stream live videos, and/or hold discussions inforums. Further, in one embodiment, the social network service mayimplement geo-social networking that co-opts Internet mapping servicesto organize user participation around geographic features and theirattributes.

In one embodiment, the social networking service may include a timeand/or a location based social network. More information regardinglocation based applications may be found in U.S. Provisional PatentApplication No. 61/511,750, filed Jul. 26, 2011, titled “SYSTEM, METHOD,AND COMPUTER PROGRAM PRODUCT FOR MANAGING A SOCIAL NETWORK BASED ON ATLEAST A TIME OR A LOCATION,” and U.S. patent application Ser. No.13/557,198, filed Jul. 24, 2012, titled “SYSTEM, METHOD, AND COMPUTERPROGRAM PRODUCT FOR MANAGING A SOCIAL NETWORK BASED ON AT LEAST A TIMEOR A LOCATION,” which are incorporated herein by reference in theirentirety.

In one embodiment, the social network system (or, again, any servicenetwork) may utilize information known about users of the social networkto generate advertisement/content suggestions and/or trigger IDs. Inanother embodiment, another system may utilize information known aboutusers of the social network to generate advertisement/contentsuggestions and/or trigger IDs (e.g. the social network system may sharethe information, etc.). For example, social network information about afirst user of the social network system may be utilized to determine oneof more advertisements/content to display to the first user. In oneembodiment, information in addition to the social network informationmay be utilized (e.g. user information provided by a retailer, etc.).

In another embodiment, the social network system may associate userswith advertisement/content trigger IDs. For example, based on userinformation associated with the social network, the user may beassociated with one or more third party advertisement/content triggerIDs 506. In one embodiment, users with similar information may beassociated with one or more of the same trigger IDs.

In one embodiment, the trigger IDs may be sent to one or my third partysystems 508 in real-time. Further, in one embodiment, the third partysystem may utilize the trigger IDs (and/or information associatedtherewith, etc.) to select one or more advertisements/content to bepresented to one or more users associated with the trigger IDs. Toaccomplish this, a data structure may be utilized to link the triggerIDs and the associated with specific advertisements/content (e.g.advertisement content, etc.) such that the latter may be looked uputilizing the former.

For example, in one embodiment, the first user of the social networkingsite may log onto an online retailer. In this case, in one embodiment,the social network system may send advertisement/content trigger IDsassociated with the first user to the online retailer (or an advertiser,etc. associated with the online retailer, etc.), such that the onlineretailer (or an advertiser, etc. associated with the online retailer,etc.) may select one or more advertisements/content to display to thefirst user (e.g. on a portion of a web page associated with the onlineretailer, etc.).

While, in the foregoing embodiment, the advertisements/content may bedisplayed to the first user via a web page, it should be noted that thetrigger IDs may be used to display the advertisement/content inconnection with any application, display, device, etc. separate from theservice network interface. Further, in any embodiment disclosed herein,the advertisement(s) itself may be sent in lieu of (or in addition to)the trigger ID(s).

In one embodiment, the third party may have one or moreadvertisements/content associated with the trigger IDs. In this way, inone embodiment, the third party may identify an advertisementopportunity (e.g. by ascertaining one of the aforementioned useridentifying aspects which correlates to a user, etc.), query the socialnetwork system for a trigger ID (e.g. that is determined by the servicenetwork by matching profile criteria known about the user (as identifiedby the user identifying aspect) with profile criteria associated withone of the trigger IDs/associated advertisements), receive the triggerID, and display one or more advertisements associated with the triggerID.

As mentioned above, in one embodiment, the third party may query thesocial network system with user information (e.g. a username, a name, analias, a user ID, a user email address, an application/locationidentifier, unique user context identifier, cookie, and/or any of theaforementioned user identifying aspects, etc.). Specifically, theservice network may track any identifying aspect of the user (e.g.anonymously or otherwise, etc.) so that such identifying aspect can beincluded with a profile-related query (e.g. to determine an appropriateadvertisement/content, if any) for display in connection with the user.

In another embodiment, the social network system may send informationassociated with one or more social network users to the third partysystem, such that the third party system may select targetedadvertisements to display to the user. In one embodiment, the user ofthe social network system may have an option to allow sharing ofinformation between the third party system and the social networksystem. Further, in one embodiment, the user may be incentivized toallow sharing between the third party system and the social networksystem. In various embodiments, the user may be incentivized byreceiving discounts, receiving credits (e.g. store credit, etc.),receiving free items, receiving money, and/or utilizing various otherincentives.

More information regarding sharing information between a socialnetworking system and a third party system, etc. may be found in U.S.Provisional Patent Application No. 61/591,819, filed Jan. 27, 2012,titled “SYSTEM, METHOD, AND COMPUTER PROGRAM PRODUCT FOR ALTERING ATLEAST ONE ASPECT OF AN INTEGRATED E-COMMERCE ON-LINE APPLICATION;” andU.S. Provisional Patent Application No. 61/596,174, filed Feb. 7, 2012,titled “SYSTEM, METHOD, AND COMPUTER PROGRAM PRODUCT FOR ALTERING ATLEAST ONE ASPECT OF AN INTEGRATED E-COMMERCE ON-LINE APPLICATION.”

Further, in one embodiment, the third party system may selectadvertisements to be displayed on a website associated with the socialnetwork system. For example, in one embodiment, information associatedwith the third party may be shared with the social network system, suchthat advertisements are presented to the user while the user isutilizing a social networking site. Additionally, in one embodiment, theadvertisements/content selected may be presented on a third partydisplay (e.g. at a business, on a billboard, etc.).

Still yet, in one embodiment, the social networking system may provideinformation (e.g. user information, trigger IDs, etc.) to companyadvertisers and/or other related-third party advertisers to triggeradvertisements. More information about providing dynamic advertisementsmay be found in U.S. Provisional Patent Application No. 61/590,764,filed Jan. 25, 2012, titled “SYSTEM, METHOD, AND COMPUTER PROGRAMPRODUCT FOR PRESENTING INFORMATION TO A USER BASED ON DETERMINEDSATISFACTION-RELATED INFORMATION ASSOCIATED WITH THE USER,” which isincorporated herein by reference in its entirety.

In one embodiment, administrators associated with the third partysystems may be capable of configuring and/or registeringadvertisement/content triggers and/or associated content/trigger IDs. Inone embodiment, the social network system may provide a GUI forconfiguring such triggers and/or advertisements. In another embodiment,an advertisement system may provide a GUI for configuring such triggers.In yet another embodiment, the third party system owner may have controlover a GUI for configuring advertisement/content triggers.

FIG. 6 shows exemplary interfaces 600 for configuring and/or registeringadvertisement/content triggers, in accordance with another embodiment.As an option, the interfaces 600 may be implemented in the context ofthe architecture and environment of the previous Figures and/or anysubsequent Figure(s). Of course, however, the interfaces 600 may beimplemented in the context of any desired environment. It should also benoted that the aforementioned definitions may apply during the presentdescription.

As shown, an advertiser may utilize one or more of the interfaces 600 toconfigure various aspects associated with triggering and/or displayingtargeted advertisements/content. In the context of the presentdescription, an advertiser refers to any entity aspiring to present aproduct, service, and/or incentive to one or more other entities (e.g.people, businesses, etc.).

As shown in interface 1, the advertiser may have the ability toassociate a trigger ID with one or more advertisement/context profiles.In one embodiment, the one or more advertisement/context profiles may beassociated with one or more advertisements/content that has beendesigned to target (or is logically attributable) to a particulardemographic or desired audience (e.g. males in their 30s, femalehomemakers, children, parents, dog owners, etc.). Accordingly, in oneembodiment, a trigger ID may be associated with profile criteria thatis, in turn, associated with one or more of the advertisements targetedtowards a specific demographic. In this way, in one embodiment, socialnetwork systems (and/or other service systems) may utilize userinformation to associate trigger IDs with users, such that when aspecific user is available for a third party advertisement opportunity,the associated trigger ID may be sent to the third party service, and anappropriate advertisement/content profile may be selected and presented,based on the trigger ID.

Further, in one embodiment, a location and/or context in which theadvertisement is to be presented may be specified. For example, invarious embodiments, an advertiser may have the ability to specify thatthe advertisements/content associated with the advertisement/contentprofile are presented at a physical display (e.g. a specific physicaldisplay, a display determined to be in proximity to the user, etc.),online (e.g. on a portion of a web page being viewed by the user, on aportion of a web page associated with the third party, on a portion of aweb page associated with a social networking site, etc.), on a mobiledevice associated with the user (e.g. via a specific screen, via aspecific application, etc.), any of the device(s) disclosed in thedescription of FIG. 4, and/or based on a location of the user.

In the case that the advertiser desires to present theadvertisement/content based on a location of the user, in oneembodiment, the advertisement/content may be presented on availabledisplays, which are determined to be in the proximity of the user (e.g.a store display, a point-of-sale terminal, etc.). In one embodiment, ifthe advertiser desires to present the advertisement/content based on alocation of the user, in one embodiment, the display in which to presentthe advertisement will be selected upon determination that the specificuser is a specific location (e.g. and/or upon another triggering event,etc.).

As shown in interfaces 2 and 3, in one embodiment, the advertiser may bepresented with specific location context options foradvertisement/content presentation. For example, in various embodiments,the advertiser may specify that the advertisement be presented at an NFCterminal, online, a mobile device associated with the user, a specificlocation display, a general area location display, a point-of-saleterminal, a specific website, a general website, and/or various otherdisplays. Furthermore, in one embodiment, the location presentationoptions may be configurable such that they are different for eachtrigger ID.

Specifically, in one embodiment in connection with interfaces 2 and 3, aspecific display may be specifically identified (e.g. utilizing an IP,GPS, or other destination address, etc.) and even given an alias (e.g.“Discount Store Sports Department Display #1,” etc.) such that aplurality of triggering profile criteria sets (each with a plurality ofcorrelating trigger IDs) may be defined and associated with suchspecific display. Further, in the event that multiple displays are beingenabled, the same or different triggering profile criteria sets/triggerIDs may be easily replicated (and possibly modified) for each of thedifferent displays. To this end, the system may be configured such that,in connection with each display, a user identifying aspect may be sentto the service network (in connection with the specific display), suchthat the user profile criteria and advertisement target profile criteriacan be used to cause display of the most relevant advertisement/contentto the user via the specific display where he/she has been identified.Yet again, while physical displays are exemplified in the currentembodiment, it should be noted that the display may be the same displaywith which the service network is accessed, but possibly in a differentcontext (e.g. during use of a separate application, during downtime,etc.).

FIG. 7 shows a system flow 700 for presenting advertisements, inaccordance with another embodiment. As an option, the system flow 700may be implemented in the context of the architecture and environment ofthe previous Figures and/or any subsequent Figure(s). Of course,however, the system flow 700 may be implemented in the context of anydesired environment. It should also be noted that the aforementioneddefinitions may apply during the present description.

As shown, a service network system may associate user profileinformation, user location information, and/or contextual informationwith one or more advertisement/content trigger IDs. For example, in oneembodiment, the service network system may utilize relevant informationassociated with a user to characterize the user such thatadvertisements/content may be targeted towards that user, based on thecharacterization. In this way, the service network system may utilize avast amount of information the system has compiled about the user tomore accurately characterize and/or categorize the user, for thepurposes of more appropriately targeting advertisements/content. In oneembodiment, the relevant profile information may be utilized toassociate a trigger ID with the user. In one embodiment, the trigger IDmay be associated with one or more advertisements/content that areconsidered to be relevant to the user.

Further, in one embodiment, user location information may be includedand/or linked to the trigger ID. In one embodiment, the user locationinformation may include current user location information. For example,in various embodiments, the current user location may be determinedbased on a user check-in, a mobile phone signal, a user communication(e.g. a user post, etc.), GPS coordinates, a network signal, a Bluetoothsignal, and/or by utilizing various other techniques.

In another embodiment, the location information may include a residencelocation associated with the user. In another embodiment, the locationinformation may include a business location associated with the user. Inanother embodiment, the location information may include a shoppinglocation associated with the user. In another embodiment, the locationinformation may include a virtual location associated with the user(e.g. a website, etc.).

Further, in one embodiment, the trigger ID may be associated with acontext. In various embodiments, the context may include situations inwhich the advertisement/content is to be displayed, a time period inwhich the advertisement/content is to be displayed (or an expirationtime, etc.), an event that is to occur before advertisement/content isto be displayed, and/or any other context in which the advertisement isto be displayed.

In one embodiment, the advertiser (and/or the service network, etc.) mayhave the ability to configure rules associated with the context. In oneembodiment, the advertiser (and/or the service network, etc.) may havethe ability to configure rules associated with the context utilizing oneor more interfaces (e.g. the interfaces of FIG. 6, etc.). In variousembodiments, the configurable rules may include configuring a number oftimes an advertisement/content is displayed to a particular user, anumber of times an advertisement/content is displayed to all users, atime of day the advertisement/content is capable of being displayed, alocation in which the advertisement/content is permitted to be displayed(e.g. a geographic location, a specific display location, a businesslocation, etc.), a demographic that is capable of viewing thecontent/advertisement, criteria that must be true for theadvertisement/content to be presented, events that must occur before theadvertisement/content is presented (e.g. the user must purchase aspecific item, the user must check-out at a store, etc.), and/or anyother rule that may be utilized to establish a context.

Furthermore, in one embodiment, the triggers IDs, which are associatedwith the information, may be associated with one or more advertisements.In one embodiment, the service network system may associate the triggerID with the advertisement(s). In another embodiment, the third partysystem may associate the trigger ID with the advertisement(s). Forexample, knowing what demographic, users, groups, and/or types of usersin which the trigger IDs are associated, the advertisements/content thatshould be directed to those users (e.g. based on market research, etc.)may be selected and associated with the trigger IDs.

Accordingly, in one embodiment, when an apparatus associated with thethird party determines that a user is present (e.g. at a point-of-saleterminal at check-out, etc.), information associated with the user maybe sent from the third party (e.g. a name, an ID, a captured image, ausername, etc.) such the service network may identify an associatedtrigger ID (or associate the user with a trigger ID, etc.). In oneembodiment, the identified (or determined) trigger ID associated withthe user may be communicated to the third party system (along with anyother information, such as context, etc.). In response, in oneembodiment, the third party system may utilize the trigger ID (as wellas any other information accompanying the trigger ID, such as context,etc.) to select one or more advertisements to display to the user.

In another embodiment, the service network system may identify thelocation of the user (e.g. based on GPS coordinates, based on a usercheck-in, based on a check-out, etc.) and send a trigger ID to the thirdparty system such that the advertisement/content may be selected anddisplayed. In still another embodiment, the service network may sendadvertisements/content to the third party system. For example, in oneembodiment, the user may be identified and one or more advertisementsmay be selected by the service network system and sent to the thirdparty system. In this case, in one embodiment, the third party systemmay display the advertisement received from the service network system.In one embodiment, the service network system may access anadvertisement database to select an advertisement to send to the thirdparty system.

FIG. 8 shows a method 800 for communicating advertisement/contenttrigger IDs, in accordance with one embodiment. As an option, the method800 may be implemented in the context of the architecture andenvironment of the previous Figures and/or any subsequent Figure(s). Ofcourse, however, the method 800 may be carried out in any desiredenvironment. It should also be noted that the aforementioned definitionsmay apply during the present description.

As shown, trigger IDs are registered with a service network. Seeoperation 802. In one embodiment, a context, user location information,and advertisement profiles may also be registered with the servicenetwork and may be associated with a trigger ID. Of course, any of thetrigger IDs and associated advertisement profile criteria and/or userprofile criteria (as disclosed herein) may be registered in operation802.

Further, it is determined whether a trigger event has occurred. Seedecision 804. In one embodiment, the service network may determinewhether the trigger event has occurred. In another embodiment, a thirdparty system may determine whether the trigger event has occurred. Inone embodiment, the third party system may determine that the triggerevent has occurred and may notify the service network system (e.g. byrequesting an advertisement, by requesting a trigger ID, by sending userinformation, etc.).

The trigger event may include any type of trigger event. For example, inone embodiment, the trigger event may include a device recognizing theface of the user. In another embodiment, the trigger event may includethe user scanning a loyalty card. In another embodiment, the triggerevent may include the user swiping a credit card. In another embodiment,the trigger event may include the user initiating a mobile walletpayment. In another embodiment, the trigger event may include the userscanning an item.

In another embodiment, the trigger event may include the user checkingin to a location. In another embodiment, the trigger event may includethe user checking out at a store. In another embodiment, the triggerevent may include the user requesting an advertisement/content. Inanother embodiment, the trigger event may include the user visiting awebsite (e.g. a particular website, etc.).

In another embodiment, the trigger event may include the user selectingan item on a web page. In another embodiment, the trigger event mayinclude the user purchasing a particular item (or any item, etc.). Inanother embodiment, the trigger event may include the user performing adesignated action on a point-of-sale terminal (e.g. selecting aparticular button, etc.). In another embodiment, the trigger event mayinclude the user performing a specific action on a mobile device (e.g.accessing a particular application, utilizing mobile paymentfunctionality, etc.).

In another embodiment, the trigger event may include receiving a signalfrom a mobile device of the user. In another embodiment, the triggerevent may include a determination that the user is in or near aparticular location. In another embodiment, the trigger event mayinclude the user accessing a particular network (e.g. a particularwireless network, etc.). In another embodiment, the trigger event mayinclude receiving a text including keywords. In another embodiment, thetrigger event may include receiving an e-mail including keywords.

In another embodiment, the trigger event may include receiving avoicemail including keywords. In another embodiment, the trigger eventmay include a calendar event. In another embodiment, the trigger eventmay include a media event. In still other embodiments, the trigger eventmay occur as a function of the identification of any of the useridentifying aspect(s) disclosed hereinabove. Of course, in variousembodiments, the trigger event may include any type of event.

If it is determined that a trigger event has occurred, theadvertisement/content trigger ID is sent to the third party system. Seeoperation 806. In one embodiment, the advertisement may be sent to thethird party system in response to the trigger event.

As noted, in one embodiment, the trigger event may include a userimplementing a transaction utilizing a mobile device.

FIG. 9 shows a system 900 for mobile device transactions, in accordancewith another embodiment. As an option, the system 900 may be implementedin the context of the architecture and environment of the previousFigures and/or any subsequent Figure(s). Of course, however, the system900 may be implemented in the context of any desired environment. Itshould also be noted that the aforementioned definitions may applyduring the present description.

As shown, an e-wallet server 902 may be in communication with one ormore mobile devices 910 and one or more point-of-sale systems 908 overone or more networks 906. Furthermore, in one embodiment, one or morestore backend servers 904 may be in communications with the e-walletserver 902, the mobile device 910, and/or the point-of-sale terminal908.

In operation, a user of the mobile device 910 may initiate a transactionutilizing the mobile device 910 and the point-of-sale terminal 908. Inone embodiment, an NFC connection between the mobile device 910 and thepoint-of-sale terminal 908 may be utilized to facilitate thetransaction. In another embodiment, a Wi-Fi direct connection betweenthe mobile device 910 and the point-of-sale terminal 908 may be utilizedto facilitate the transaction.

In another embodiment, an IR connection between the mobile device 910and the point-of-sale terminal 908 may be utilized to facilitate thetransaction. In another embodiment, a Bluetooth connection between themobile device 910 and the point-of-sale terminal 908 may be utilized tofacilitate the transaction. In another embodiment, bump technologyimplemented between the mobile device 910 and the point-of-sale terminal908 may be utilized to facilitate the transaction.

In another embodiment, the transaction between the mobile device 910 andthe point-of-sale terminal 908 may be facilitated over the network 906(or another network, the Internet, etc.). In another embodiment,information displayed on the mobile device 910 may be scanned by thepoint-of-sale terminal 908 to facilitate the transaction. Of course, invarious embodiments, any suitable technology may be utilized tofacilitate the transaction.

In operation, in one embodiment, the user may utilize an e-walletapplication 912, which is stored on the mobile device 910 to facilitatepayment of goods and/or services. In one embodiment, the e-walletapplication 912 may enable communication between the mobile device 910and the e-wallet server 902. In one embodiment, the e-wallet server 902may include service functionality for enabling a transaction to occurbetween the user of the mobile device 910 and a store associated withthe point-of-sale terminal and/or the store backend server 904.

For example, a user may proceed to checkout at a point-of-sale terminalat a grocery store. In one embodiment, the mobile device 910 may beutilized to communicate store loyalty card information to thepoint-of-sale terminal 908. In one embodiment, a store application 914,which may be stored on the mobile device 910, may be utilized tofacilitate the transfer of the store loyalty card information. Inanother embodiment, the e-wallet application 912 may be utilized tofacilitate the transfer of the store loyalty card information.

Further, in one embodiment, the user may utilize the e-walletapplication 912 stored on the mobile device 910 to pay for items. In oneembodiment, the e-wallet application 912 may include credit cardinformation associated with the user, such that the credit card may beutilized automatically to pay for the items. In another embodiment, thee-wallet application 912 may include pre-paid card informationassociated with the user, such that the pre-paid card may be utilizedautomatically to pay for the items. In another embodiment, the e-walletapplication 912 may include bank card information associated with theuser, such that the bank card may be utilized automatically to pay forthe items. In another embodiment, the e-wallet application 912 mayinclude bank account information associated with the user, such that thebank account information may be utilized automatically to pay for theitems. In one embodiment, a user may have the ability to choose adefault payment method from a list of available payment methods.

In one embodiment, transaction details may be displayed on the mobiledevice 910 and/or on a display associated with the point-of-sale system908. For example, in one embodiment, upon finalization of thetransaction, transaction information may be displayed on the mobiledevice. In one embodiment, the transaction information may be displayedutilizing the e-wallet application 912.

In another embodiment, the transaction information may be displayedutilizing the store application 914. In another embodiment, thetransaction information may be displayed utilizing another applicationstored on the mobile device 910. Further, in one embodiment, thetransaction information may be displayed on a lock screen of the mobiledevice 910. In one embodiment, such transaction information may bedisplayed in a non-intrusive manner. In various embodiments, thetransaction information may include a cost (e.g. a total cost, a costper item, a cost of sales tax, an itemized price list, etc.), a list ofpurchased items/services, a time of purchase, product names, productcodes, a method of payment, one or more of the transaction parties,and/or any other transaction related information.

Still yet, in one embodiment, the transaction may serve as trigger eventfor displaying advertisements on the point-of-sale terminal 908 and/orthe mobile device, as described in the context of the previous figuresand subsequent figures (such as FIG. 13), etc. In one embodiment, theadvertisements may be displayed on the mobile device 910 and/or thepoint-of-sale terminal 908 in a non-intrusive manner.

More information about non-intrusively displaying advertisements on amobile device may be found in U.S. Provisional Patent Application No.61/711,727, filed Oct. 9, 2012, titled “SYSTEM, METHOD, AND COMPUTERPROGRAM PRODUCT FOR DETERMINING WHETHER TO PROMPT AN ACTION BY APLATFORM IN CONNECTION WITH A MOBILE DEVICE,” which is incorporatedherein by reference in its entirety.

FIG. 10 shows a method 1000 for a mobile device transaction, inaccordance with another embodiment. As an option, the method 1000 may beimplemented in the context of the architecture and environment of theprevious Figures and/or any subsequent Figure(s). Of course, however,the method 1000 may be carried out in any desired environment. It shouldalso be noted that the aforementioned definitions may apply during thepresent description.

As shown, it is determined whether an NFC trigger is received by amobile device (or an application associated therewith). Seedetermination 1002. While a NFC trigger is disclosed in the context ofoperation 1002, it should be noted that any connection mechanism (e.g.see those, for example, disclosed during the description of FIG. 9,etc.) may be used in lieu of NFC.

If a trigger is received in operation 1002, information associated withthe transaction is received, a payment method is selected (e.g. a cardis selected, etc.), and a loyalty card is identified. See operation1004.

In one embodiment, the information received may include transactioninformation. In various embodiments, the transaction information mayinclude a price, credit card information, loyalty information, productinformation, store information, time information, location information,discount information, method of purchase information, and/or any othertype of transaction-related information.

In various embodiments, the payment method may include a credit card (ora credit card number), a debit card, a prepaid card, bank accountinformation, and/or any other payment type. In one embodiment, thepayment method may be manually selected by the user at the time ofcompleting the transaction. Further, in another embodiment, the paymentmethod may be automatically selected (or at least suggested) based onany criteria. Such criteria may include or be based, at least in part,on a current location (e.g. based on a GPS location, etc.), apoint-of-sale terminal used, on a signal received (e.g. that indicateswhich payment method types are acceptable), the type of payment methodlast used (in general, or at the current location), a balance of anaccount associated with the payment method (that is sufficient to coverthe cost of the transaction), etc.

Still yet, in operation 1004, a loyalty card may be identified. Forexample, such loyalty card may be automatically selected. In variousembodiments, the loyalty card may be selected based on a currentlocation (e.g. based on a GPS location, etc.), based on a point-of-saleterminal used, based on a signal received, and/or utilizing variousother techniques. In another embodiment, the loyalty card may bemanually selected by the user of the mobile device.

Further, it is determined whether a screen of the mobile device islocked. See determination 1006. If it is determined that the screen islocked, the transaction details are displayed on the screen lock screenof the mobile device. See operation 1008. If it is determined that thescreen is not locked, the transaction details are displayed on the mainscreen of the mobile device. See operation 1010.

While not necessarily illustrated, it may or may not be determinedwhether the mobile device is in a standby mode in determination 1006. Ifit is determined that the mobile device is in a standby mode, the mobiledevice may be powered up and/or taken out of the standby mode before thetransaction details are displayed on the screen lock screen of themobile device in operation 1008.

In the event that the transaction details are displayed on the mainscreen of the mobile device per operation 1010, an application (e.g.e-wallet, etc.) installed on the mobile device (that is capable offacilitating the transaction) may be automatically executed and opened,such that the main screen is populated (possibly entirely orsubstantially so) by an interface of the aforementioned application.

While not shown, in the event that a transaction is completed via thelock screen in operation 1008, an option may be given thereafter toexecute and open a relevant interface (e.g. post-transaction interface)of the foregoing application for engaging in post-transactionfunctionality (e.g. examples of which will be set forth hereinafter ingreater detail). Further, absent electing such option, the mobile devicemay either stay in lock screen mode for a predetermined period andthereafter return to the power standby mode, or immediately return tothe power standby mode.

In one embodiment, one or more advertisements may be displayed on thelock screen of the mobile device (and/or the main screen, as well).Further, in one embodiment, advertisements may be displayed on themobile device based on a location of the mobile device.

Again, it should be noted that, although the method 1000 refers to anNFC trigger, any communication protocol connection may be utilized as atrigger in another embodiment.

FIG. 11 shows a method 1100 for a mobile device transaction, inaccordance with another embodiment. As an option, the method 1100 may beimplemented in the context of the architecture and environment of theprevious Figures and/or any subsequent Figure(s). Of course, however,the method 1100 may be carried out in any desired environment. It shouldalso be noted that the aforementioned definitions may apply during thepresent description.

As shown, it is determined whether a location trigger is received by amobile device. See determination 1102. In one embodiment, the locationtrigger may include any of the user identifying aspects set forthhereinabove during the description of FIG. 4. In other embodiments, thelocation trigger may include any trigger associated with locationdetermination. Further, the location of the user and/or the mobiledevice may be determined utilizing a variety of techniques.

For example, in one embodiment, the user may digitally check-in to alocation and the location may be determined. In various embodiments, theuser may check-in to the location utilizing the mobile device associatedwith the user, a system associated with the location, and/or anotherdevice. In one embodiment, the user may check in to a location utilizingan application stored on the mobile device of the user. In variousembodiments, the application may include a social network application,an application associated with the location, a mapping application, ageo-caching application, and/or various other applications. In anotherembodiment, the user may check in to a location utilizing a check-insystem associated with the location.

In another embodiment, the mobile device of the user may be utilized toautomatically check in to a location. For example, in one embodiment, anapplication stored on the mobile device may be utilized to automaticallycheck in to a location (e.g. based on a wireless signal, based onwireless network availability, based on GPS, a bump signal, an NFCsignal, a Wi-Fi signal, etc.).

Further, in one embodiment, the location of the user and/or mobile maybe determined based on GPS. For example, the mobile device (and/or anapplication/OS associated therewith) may share GPS data associated withthe mobile device, such that the location of the mobile device/user isdetermined. In one embodiment, the GPS data may be shared with theservice network system. In another embodiment, the GPS data may beshared with one or more third party systems.

In another embodiment, the location of the user and/or the mobile devicemay be determined based on a signal provided by the mobile device of theuser. For example, in one embodiment, the mobile device of the user mayprovide a Bluetooth signal that is capable of being received by a deviceassociated with the location (e.g. a display, a computer, a locationdetection device, a point-of-sale device, etc.), such that location maybe determined. In another embodiment, the mobile device of the user mayprovide a NFC signal that is capable of being received by a deviceassociated with the location (e.g. a display, a computer, a locationdetection device, a point-of-sale device, etc.), such that location maybe determined. In another embodiment, the mobile device of the user mayprovide a Wi-Fi signal that is capable of being received by a deviceassociated with the location (e.g. a router, a display, a computer, alocation detection device, a point-of-sale device, etc.), such thatlocation may be determined. In another embodiment, the mobile device ofthe user may provide a chirp signal that is capable of being received bya device associated with the location, such that location may bedetermined. In one embodiment, the chirp signal may include informationassociated with the location (e.g. GPS coordinates, etc.). In oneembodiment, a signal strength associated with the chirp may be used toassociate the user with a location.

In another embodiment, the mobile device may be connected to a wirelessnetwork associated with the location automatically (or manually), suchthat a location may be determined. In still another embodiment, thelocation of the user may be determined utilizing facial recognitiontechniques. For example, in one embodiment, a system associated with thelocation may be utilized to determine the user is present based onfacial recognition.

In another embodiment, the location of the user may be determinedutilizing social network status associated with the user. In anotherembodiment, the location of the user may be determined based on anaction of the user. For example, in one embodiment, the user may utilizethe mobile device to scan a bar code of an item (e.g. a product, aposter, a billboard, etc.), such that the location of the user may bedetermined. In another embodiment, the user may utilize the mobiledevice to capture an image of an item (e.g. a building, a sign, aproduct, a poster, a billboard, etc.), such that the location of theuser may be determined.

In another embodiment, the user may utilize the mobile device tofacilitate a purchase at a location (e.g. utilizing an e-walletapplication, utilizing a digital credit card, utilizing a digital debitcard etc.), such that the location of the user may be determined. Inanother embodiment, the user may utilize a payment techniqueattributable to the user to facilitate a purchase at a location (e.g.utilizing gift card, utilizing a credit card, utilizing a debit cardetc.), such that the location of the user may be determined. In anotherembodiment, the user may scan a loyalty card at a location, such thatthe location of the user may be determined. Of course, any technique maybe utilized to determine a location associated with the user.Furthermore, in various embodiments, any location determination eventmay include receiving a location trigger.

If it is determined that a location trigger is received, a locationapplication is automatically executed on the mobile device. Seeoperation 1104. In one embodiment, the location application may includean application associated with a business (e.g. a business at thelocation, etc.). In another embodiment, the location application mayinclude an application associated with an advertiser. In anotherembodiment, the location application may include an applicationassociated with a mobile e-wallet application.

Once the location application is executed, in one embodiment,pre-experience functionality is implemented. See operation 1106. Whilethe functionality of operation 1106 is set forth in the context of alocation application that is triggered by a location trigger event, itshould be noted that it is contemplated that operation 1106 may occurindependent of location, as well, in other embodiments.

In one embodiment, the pre-experience functionality may includereceiving advertisements/deals/coupons on the mobile device, apoint-of-sale terminal display, and/or a display associated with thelocation. In one embodiment, the advertisements may includeadvertisements specifically targeted towards the user of the mobiledevice (e.g. as described in the context of the previous figures, etc.).Further, in one embodiment, the advertisements may includeadvertisements that are associated with the location (e.g. storeadvertisements associated with the location, product advertisementsassociated with the location, service advertisements associated with thelocation, etc.). Still yet, the aforementionedadvertisements/deals/coupons may be specifically targeted as to thespecific location of the user. For example, a user may receive a firstadvertisement for a first product in a first aisle if it is determinedthat the user is in the first aisle, a second advertisement for a secondproduct in a second aisle if it is determined that the user is in thesecond aisle, and/or a third advertisement for a third product in acheckout line if it is determined that the user is in the checkout line.

Still yet, in one embodiment, deals and/or incentivized group discountsmay be presented to the user. More information regarding groupincentivized discounts may be found in U.S. Provisional PatentApplication No. 61/590,767, filed Jan. 25, 2012, and titled “SYSTEM,METHOD AND COMPUTER PROGRAM PRODUCT FOR LOCATION-SPECIFIC PRIVACYSETTINGS.”

Further, in one embodiment, the pre-experience functionality may includereceiving additional purchase suggestions. For example, in oneembodiment, a user may scan one or more items at a point-of-saleterminal, and initiate a payment utilizing the mobile device, such thatthe location is determined, the location trigger is received, and thelocation application is executed. In this case, in one embodiment,additional item suggestions may be made to the user for purchase, basedon scanned items. In another embodiment, items may be suggested to theuser based on previous purchases. In addition to basing suggestions onthe foregoing, such suggestions may be made as a function of anaccessibility of the product. For example, if the user is already in acheck-out line, the suggestion product may be accessible from thecheck-out line. Of course, in various embodiments, items may besuggested to the user based on any techniques discussed herein.Additionally, in one embodiment, items may be suggested to the userbased on determined interests. In one embodiment, the interests may bedetermined utilizing user information gleaned from service networks(e.g. a social media network, etc., as described herein, etc.).

More information regarding determining interests/habits of a user may befound in U.S. Provisional Patent Application No. 61/481,722, filed May2, 2011, titled “SYSTEM, METHOD, AND COMPUTER PROGRAM PRODUCT FORALLOCATING TIME TO ACHIEVE OBJECTIVES;” and U.S. patent application Ser.No. 13/462,804, filed May 2, 2012, titled “SYSTEM, METHOD, AND COMPUTERPROGRAM PRODUCT FOR ALLOCATING TIME TO ACHIEVE OBJECTIVES,” which areincorporated herein by reference in their entirety.

Further, in one embodiment, the pre-experience functionality may includedetermining whether the user desires to use paper or plastic bags. Forexample, in one embodiment, the user may be presented with the option touser paper or plastic bags on the mobile device. In one embodiment,selection of paper or plastic may cause the appropriate bag to bedispensed for use (e.g. utilizing an automatic dispenser, etc.). In oneembodiment, the user may have the option to select a number of bags. Inone embodiment, the user may be automatically charged for the bags, uponselection of the number of bags. In one embodiment, the user may bepresented with the option to confirm the desire to purchase bags, on themobile device.

In still another embodiment, the pre-experience functionality mayinclude loyalty building by presenting the user with informationregarding the relevant business, store, establishment, etc. For example,such functionality may provide access to an order menu for communicatinga real-time order for a product (e.g. sandwich order, coffee order,etc.), current gift/store card balance, rewards, nutritionalinformation, links to product websites, past purchase history, upcomingevents, registration form for joining a loyalty program, productrefill/replenishment suggestions that are a function oftime/date-stamped past purchases and estimated/predetermined time-based(or other) thresholds that indicate when a refill/replenishment wouldlikely be necessary, wish lists that allow a user to track their desiredproducts and/or products that are desired by friends/family/colleaguesof the user (as possibly indicated by links, information, etc. sharedwith the user), notes, etc.

As an option, in one possible embodiment, any of the pre-transactionexperience functionality may be facilitated by way of the automaticexecution of a business-specific application. In such embodiment, thebusiness-specific application may be utilized to provide any of thepre-experience functionality set forth herein.

In one embodiment, the purchase may be capable of being facilitatedutilizing NFC functionality between the mobile device and apoint-of-sale terminal. In this case, it is determined whether an NFCtrigger is received. See decision 1108. Of course, in other embodiments,any suitable technology may be utilized to facilitate the transaction(e.g. bump technology, Wi-Fi direct, Bluetooth, location, any of thosementioned hereinabove, etc.).

If it is determined that the NFC trigger is received, a paymentauthorization or process is executed. See operation 1110. In variousembodiments, the payment authorization/process may include credit cardauthorization, payment authorization, user verification/authentication,a user confirmation prompt, and/or various other processes. Further, asan option, such trigger automatically cease the pre-transactionexperience and immediately present transaction information using any ofthe techniques disclosed herein. As a further option, in the event auser has engaged in any of the aforementioned pre-transactionexperience, such user may be given the option to escalate to the paymentauthorization or process in response to the selection of an icon (e.g.after the user has deemed that he/she has completed the pre-transactionexperience.

FIG. 12 shows a method 1200 for a mobile device transaction, inaccordance with another embodiment. As an option, the method 1200 may beimplemented in the context of the architecture and environment of theprevious Figures and/or any subsequent Figure(s). Of course, however,the method 1200 may be carried out in any desired environment. It shouldalso be noted that the aforementioned definitions may apply during thepresent description.

As shown, a mobile device is initialized. See operation 1202. In oneembodiment, the mobile device may be initialized based on a proximity toanother device (e.g. a point-of-sale device, etc.). In anotherembodiment, the mobile device may be initialized based on the depressionof a home key.

In another embodiment, the mobile device may be initialized upon achange from a sleep mode to a standby mode. In another embodiment, themobile device may be initialized upon a change from a standby mode to anon mode (e.g. power up mode). In another embodiment, the mobile devicemay be initialized upon receiving a signal from the user.

In another embodiment, the mobile device may be initialized uponreceiving a signal from an application. In another embodiment, themobile device may be initialized upon establishment of an NFC connection(e.g. with a point-of-sale terminal, etc.). Of course, in variousembodiments, the mobile device may be initialized in a variety of ways.By way of further example, initialization may be prompted with any ofthe aforementioned user identifying aspects described during referenceto FIGS. 3-8, any of the techniques described in connection withoperation 1002 of FIG. 10, and/or anything else that is capable oftriggering initialization, for that matter.

Once the mobile device is initialized, information associated with thetransaction, including a total amount, is received. See operation 1204.The information associated with the transaction may include anytransaction related information.

Further, loyalty information is identified. See operation 1206. In oneembodiment, the loyalty information may be identified automatically. Inanother embodiment, the loyalty information may be identified manually(e.g. upon selection of a card, etc.). Of course, the loyaltyinformation may be identified in any desired manner (e.g. see, forexample, the description of operation 1004 of FIG. 10, etc.).

Additionally, a payment method is selected based on user history orpreferences. See operation 1208. For example, in one embodiment, theuser may have selected a particular payment method to be a defaultpayment method. In another embodiment, the user may have utilized aparticular payment method on one or more previous occasions, such thatthe payment method it determined to be used based on history.

In various embodiments, the payment method may include a credit card (ora credit card number), a debit card, a prepaid card, bank accountinformation, and/or any other payment type. In one embodiment, thepayment method may be manually selected by the user at the time ofcompleting the transaction. Further, in another embodiment, the paymentmethod may be automatically selected (or at least suggested) based onany criteria. Such criteria may include or be based, at least in part,on a current location (e.g. based on a GPS location, etc.), apoint-of-sale terminal used, on a signal received (e.g. that indicateswhich payment method types are acceptable), the type of payment methodlast used (in general, or at the current location), a balance of anaccount associated with the payment method (that is sufficient to coverthe cost of the transaction), etc.

Still yet, transaction information is displayed for approval. Seeoperation 1210. In one embodiment, the transaction information may bedisplayed on the mobile device. In another embodiment, the transactioninformation may be displayed on a point-of-sale terminal (in addition toor in lieu of display on the mobile device). In one embodiment, thetransaction information may be displayed along with a selection optionto approve and/or confirm the transaction. In another embodiment, thetransaction information may be displayed along with a selection optionto go back to a previous step in the transaction process (e.g. to enterloyalty information, etc.). More information regarding various optionaltechniques with which the transaction information may be displayed onthe mobile device will be set forth hereinafter in greater detail duringreference to subsequent figures.

Further, it is determined whether an NFC connection (or any session thatwas triggered by the initialization of operation 1202) is stillavailable. See determination 1212. If a connection is not stillavailable, it is determined whether a connection can be reestablished.See operation 1214. If a connection cannot be reestablished, the mobiledevice (or an application associated therewith) determines whether thereis a timeout. See decision 1216. If it is determined that there is atimeout, the transaction process is terminated on the mobile device andthe application is closed. See operation 1218.

If a connection is still available, it is determined whether purchaseconfirmation is received from the user. See determination 1220. In oneembodiment, the purchase confirmation may include the user selecting aconfirmation icon presented on the mobile device, sliding a slider,performing a predetermined gesture, entering a pass code, scanning afingerprint/face, and/or any other desired user input. In anotherembodiment, the user may have an option to confirm the purchaseutilizing a point-of-sale terminal associated with the transaction.

If it is determined that confirmation is received, an authorization codeis transferred. See operation 1222. In one embodiment, the authorizationcode may be transmitted from the mobile device to the point-of-saleterminal. In another embodiment, the authorization code may betransmitted from the mobile device to a store backend server. In anotherembodiment, the authorization code may be transmitted from the mobiledevice to a payment server.

Once the transaction is complete, an electronic receipt may be received.See operation 1224. In one embodiment, the electronic receipt may bereceived over the connection between the point-of-sale terminal and themobile device (e.g. the NFC connection, etc.). In another embodiment,the electronic receipt may be received via a text message (e.g. an MMS,an SMS, etc.).

In another embodiment, the electronic receipt may be received via anemail. In another embodiment, the electronic receipt may be receivedover a network (e.g. accessed by a website, etc.). In anotherembodiment, the electronic receipt may be received by an applicationstored on the mobile device (e.g. an e-wallet application, a storeapplication, etc.). In another embodiment, the electronic receipt may bestored on a network server (e.g. in a network cloud, etc.).

Furthermore, in one embodiment, the transaction may be logged. Seeoperation 1226. In one embodiment, the transaction may be logged on themobile device. In another embodiment, the transaction may be logged in adatabase associated with the store. In another embodiment, thetransaction may be logged in a database associated with the paymentfacilitator. In another embodiment, the transaction may be logged in adatabase associated with a service provider (e.g. an advertiser, asocial network, etc.).

In one embodiment, post-purchase functionality is triggered. Seeoperation 1228. While operation 1128 is shown to occur after operation1126, it should be noted that operation 1128 may occur immediately (orshortly) after determination 1220. For that matter, any of theoperations disclosed herein (in any of the Figures) may be re-ordered asdesired, as well as removed and/or subject to additional intermediateoperations.

In various embodiments, the post-purchase functionality may includedisplaying advertisements, displaying shopping suggestions, displayingdiscounts, displaying options for products not purchased, displayingcontact information associated with the transaction or a potentialfuture transaction, displaying a survey and/or satisfaction relatedquestions, and/or various other post-purchase functionality.

As an option, in one possible embodiment, any of the post-transactionexperience functionality may be facilitated by way of the automaticexecution of a business-specific application. In such embodiment, thebusiness-specific application may be utilized to provide any of thepost-experience functionality set forth herein. Further, suchbusiness-specific application may interface with an e-wallet applicationfor sharing information (e.g. transaction information, purchasestatistics, profile information, etc.) for providing and/or supportingthe post-experience functionality.

In one embodiment, advertisers may utilize the completion of thetransaction as a target advertisement trigger event. For example, in oneembodiment, the owner of a presentation medium (e.g. a store, etc.) maybe in communication with one or more service networks, such thatadvertisements may be presented at a time of sale.

FIG. 13 shows a system flow 1300 for presenting advertisements, inaccordance with another embodiment. As an option, the system flow 1300may be implemented in the context of the architecture and environment ofthe previous Figures and/or any subsequent Figure(s). Of course,however, the system flow 1300 may be implemented in any desiredenvironment. It should also be noted that the aforementioned definitionsmay apply during the present description.

As shown, a third party advertiser registers one or more advertisements,which are associated with one or more profile triggers, with a servicenetwork. See step 1. This may or may not, for example, encompass any ofthe trigger IDs and related information described hereinabove inconnection with FIGS. 1-9, in one embodiment.

Further, a third party owner of a presentation medium registers one ormore presentation mediums, including location/context information and acontext medium specification, with the service network. See step 2. Thelocation/context information may include any IP or destination addressand/or any other identifier capable of being used to directadvertisements (or trigger IDs) thereto. Further, the context mediumspecification may identify any formatting/protocol/etc. that is capableof being used to ensure that the advertisements selected for and/ordirected to the presentation medium are formatted for proper deliveryand/or presentation.

The service network then identifies a profile trigger that also maytrigger on location/context information of a registered presentationdevice. See step 3. In one embodiment, this may or may not beaccomplished in a manner similar to that set forth during thedescription of FIGS. 1-9. For instance, a user identifying aspect may bereceived in connection the registered presentation device. Further, inresponse to such user identifying aspect, an advertisement/content maybe identified by matching advertisement/content profile criteria withuser profile criteria. See step 4.

Further, the service network transforms the selected advertisement,based on a medium specification. Again, see step 4.

Additionally, the service network pushes one or more advertisements to acorresponding presentation medium with a time stamp. See step 5.Subsequently, the advertisement is displayed within the time period ofthe time stamp. See step 6. Furthermore, in one embodiment, the servicenetwork may confirm display of the advertisement. See step 7.

Still yet, the display of the advertisement is reported to the thirdparty advertiser. See step 8. As a result, the third party advertisermay pay for the advertisement display. See step 9. Moreover, in oneembodiment, the service network may share payment with and/or otherwiseincentivize the third party presentation medium owner. See step 10.

In one embodiment, the advertisement may be presented on a mobile deviceof the user. Further, in one embodiment, the advertisement may bepresented on the mobile device screen, along with transaction detailsassociated with a sale. Still yet, in one embodiment, the mobile devicemay be utilized to facilitate the transaction and/or trigger advertisingevents.

FIG. 14 shows a mobile device interface 1400 for facilitating a payment,in accordance with another embodiment. As an option, the systeminterface 1400 may be implemented in the context of the architecture andenvironment of the previous Figures and/or any subsequent Figure(s). Ofcourse, however, the interface 1400 may be implemented in any desiredenvironment. It should also be noted that the aforementioned definitionsmay apply during the present description.

As shown, upon initialization of a payment process, in one embodiment,transaction information may be shown on a lock screen of a mobile devicescreen. Further, in one embodiment, additional alerts may be capable ofbeing displayed on the screen (e.g. text message alerts, calendaralerts, incoming call alerts, voicemail alerts, etc.).

In one embodiment, the transaction details displayed on the screen mayinclude a total amount, a preferred or selected method of payment (e.g.the Visa Card ending in *3232, etc.), loyalty card information, and/orvarious other information. Further, in one embodiment, the user may bepresented with an option to accept payment. In one embodiment, theoption to select payment may include a button. In another embodiment,the option to select payment may include a slider. In anotherembodiment, the option to select the payment may include a passcodeentry. In another embodiment, the option to select the payment mayinclude a biometric data entry portion.

FIG. 15 shows a mobile device interface 1500 for facilitating a payment,in accordance with another embodiment. As an option, the systeminterface 1500 may be implemented in the context of the architecture andenvironment of the previous Figures and/or any subsequent Figure(s). Ofcourse, however, the interface 1500 may be implemented in any desiredenvironment. It should also be noted that the aforementioned definitionsmay apply during the present description.

As shown, upon initialization of a payment process, in one embodiment,transaction information may be shown on a password entry screen of amobile device. Further, in one embodiment, additional alerts may becapable of being displayed on the screen (e.g. text message alerts,calendar alerts, incoming call alerts, voicemail alerts, etc.). In oneembodiment, the user may have the ability to enter an alpha-numericpassword to authorize the transaction. As an option, such alpha-numericpassword may be the same or different from the alpha-numeric passwordused to unlock the screen lock screen (to access the menu, etc.).

FIG. 16 shows a mobile device interface 1600 for facilitating a payment,in accordance with another embodiment. As an option, the systeminterface 1600 may be implemented in the context of the architecture andenvironment of the previous Figures and/or any subsequent Figure(s). Ofcourse, however, the interface 1600 may be implemented in any desiredenvironment. It should also be noted that the aforementioned definitionsmay apply during the present description.

As shown, upon initialization of a payment process, in one embodiment,transaction information may be shown on a passcode entry screen of amobile device. Further, in one embodiment, additional alerts may becapable of being displayed on the screen (e.g. text message alerts,calendar alerts, incoming call alerts, voicemail alerts, etc.). In oneembodiment, the user may have the ability to enter a numeric passcode toauthorize the transaction. In one embodiment, the numeric passcode mayinclude the same passcode for accessing additional phone/e-mail/mobiledevice menu functionality.

FIG. 17 shows a mobile device interface 1700 for facilitating a payment,in accordance with another embodiment. As an option, the systeminterface 1700 may be implemented in the context of the architecture andenvironment of the previous Figures and/or any subsequent Figure(s). Ofcourse, however, the interface 1700 may be implemented in any desiredenvironment. It should also be noted that the aforementioned definitionsmay apply during the present description.

As shown, upon initialization of a payment process, in one embodiment,transaction information may be shown on a passcode entry screen of amobile device. Further, in one embodiment, additional alerts may becapable of being displayed on the screen (e.g. text message alerts,calendar alerts, incoming call alerts, voicemail alerts, etc.). In oneembodiment, the user may have the ability to present a face image toauthorize the transaction. For example, in one embodiment, the user mayutilize a camera of the mobile device to capture one or images ofhis/her face such that a facial recognition process may be utilized todetermine whether to authorize the payment.

Once the payment has been confirmed, in one embodiment, post-paymentfunctionality may be presented to the user on the mobile device.

FIG. 18 shows a mobile device interface 1800 for presenting post-paymentfunctionality, in accordance with another embodiment. As an option, thesystem interface 1800 may be implemented in the context of thearchitecture and environment of the previous Figures and/or anysubsequent Figure(s). Of course, however, the interface 1800 may beimplemented in any desired environment. It should also be noted that theaforementioned definitions may apply during the present description.

As shown, in one embodiment, the post-payment functionality may bepresented on a lock screen associated with the mobile device. In oneembodiment, the post-payment functionality may include displaying analert or notification indicating that the payment/transaction wassuccessful. In another embodiment, the post-payment functionality mayinclude displaying advertisements on the mobile device screen. In oneembodiment, the advertisement may be provided by the business associatedwith the transaction. In another embodiment, the advertisement may beprovided by a service provider (e.g. a social network service, etc.). Inanother embodiment, the advertisement may be provided by an advertiser.Of course, the advertisement may be provided based on any of thetechniques described herein (e.g. targeted based on user information,etc.). See, for example, the description of FIGS. 1-9, in accordancewith one embodiment.

As an option, content/icons/options, etc. of the interfaces of FIGS.14-18 may be displayed for facilitating the initiation and completion ofan e-wallet transaction without necessarily having to manually removethe mobile device from a standby mode, and without necessarily leavingthe lock-screen. Of course, in other embodiments, initiation andcompletion of the e-wallet transaction with manual initiation andnon-lock-screen functionality is contemplated, as well.

In still other embodiments, the ability to initiate and/or completee-wallet transactions via the lock screen (see FIGS. 14-18) may bedisabled (i.e. selectively enabled) via a settings interface. When suchfunctionality is disabled, the e-wallet transaction may be initiatedand/or completed via an e-wallet application interface screen (that maybe accessed via a main menu screen, etc.).

Further, in one embodiment, the user may be presented with an option toreceive targeted advertisements based on purchase, at a current timeand/or in the future. Additionally, in one embodiment, the user may bepresented with the option to share information (e.g. transactioninformation, purchase information, personal information, etc.) with oneor more other systems (e.g. advertisers, etc.).

As an option, the aforementioned mobile device may be capable ofoperating in a location-specific mode. Specifically, in one embodiment,a location associated with the mobile device may be determined. Furtherdetermined may be a presence of at least one other person at thelocation. Still yet, a graphical user interface may be automaticallydisplayed. Such graphical user interface may be specifically associatedwith the determined location and the determined presence of the at leastone other person. In another embodiment, the system, method, or computerprogram product may be capable of determining a location associated withthe mobile device and automatically determining that the location isproximate to a previously identified item of interest. To this end, agraphical user interface associated with the determined location and thepreviously identified item of interest may be displayed. Moreinformation regarding such location-specific features that may or maynot be incorporated into any of the embodiments disclosed herein, may befound in U.S. patent application Ser. No. 13/652,458, filed Oct. 15,2012, titled “MOBILE DEVICE SYSTEM, METHOD, AND COMPUTER PROGRAMPRODUCT,” which is incorporated herein by reference in its entirety.

In various other optional embodiments, the features, capabilities,and/or technology, etc. of the television, mobile devices, and/or mobiledevice applications, etc. disclosed in the followingpatents/applications may or may not be incorporated into any of theembodiments disclosed herein: U.S. Pat. No. 8,078,397, U.S. Pat. No.7,669,123, U.S. Pat. No. 7,725,492, U.S. Pat. No. 7,788,260, U.S. Pat.No. 7,797,256, U.S. Pat. No. 7,809,805, U.S. Pat. No. 7,827,208, U.S.Pat. No. 7,827,265, U.S. Pat. No. 7,890,501, U.S. Pat. No. 7,933,810,U.S. Pat. No. 7,945,653, U.S. Pat. No. 7,970,657, U.S. Pat. No.8,010,458, U.S. Pat. No. 8,027,943, U.S. Pat. No. 8,037,093, U.S. Pat.No. 8,081,817, U.S. Pat. No. 8,099,433, US20080033739A1,US20080046976A1, US20090144392A1, US20090198487A1, US20100049852A1,US20100132049A1, US20100164957A1, US20100169327A1, US20100198581A1,US20100229223A1, US20100257023A1, and/or US20110044354A1. Each of theforegoing patents/applications are hereby incorporated by reference intheir entirety for all purposes.

The elements depicted in flow charts and block diagrams throughout thefigures imply logical boundaries between the elements. However,according to software or hardware engineering practices, the depictedelements and the functions thereof may be implemented as parts of amonolithic software structure, as standalone software modules, or asmodules that employ external routines, code, services, and so forth, orany combination of these, and all such implementations are within thescope of the present disclosure. Thus, while the foregoing drawings anddescription set forth functional aspects of the disclosed systems, noparticular arrangement of software for implementing these functionalaspects should be inferred from these descriptions unless explicitlystated or otherwise clear from the context.

It will be appreciated that the various steps identified and describedabove may be varied, and that the order of steps may be adapted toparticular applications of the techniques disclosed herein. All suchvariations and modifications are intended to fall within the scope ofthis disclosure. As such, the depiction and/or description of an orderfor various steps should not be understood to require a particular orderof execution for those steps, unless required by a particularapplication, or explicitly stated or otherwise clear from the context.

The methods or processes described above, and steps thereof, may berealized in hardware, software, or any combination of these suitable fora particular application. The hardware may include a general-purposecomputer and/or dedicated computing device. The processes may berealized in one or more microprocessors, microcontrollers, embeddedmicrocontrollers, programmable digital signal processors or otherprogrammable device, along with internal and/or external memory. Theprocesses may also, or instead, be embodied in an application specificintegrated circuit, a programmable gate array, programmable array logic,or any other device or combination of devices that may be configured toprocess electronic signals.

It will further be appreciated that one or more of the processes may berealized as computer executable code created using a structuredprogramming language such as C, an object oriented programming languagesuch as C++, or any other high-level or low-level programming language(including assembly languages, hardware description languages, anddatabase programming languages and technologies) that may be stored,compiled or interpreted to run on one of the above devices, as well asheterogeneous combinations of processors, processor architectures, orcombinations of different hardware and software.

In one embodiment, each method described above and combinations thereofmay be embodied in computer executable code that, when executing on oneor more computing devices, performs the acts and/or provides thecapabilities thereof. In another embodiment, the methods may be embodiedin systems that perform the acts and/or provides the capabilitiesthereof, and may be distributed across devices in a number of ways, orall of the functionality may be integrated into a dedicated, standalonedevice or other hardware. In another embodiment, means for performingthe steps associated with the processes described above may include anyof the hardware and/or software described above. All such permutationsand combinations are intended to fall within the scope of the presentdisclosure.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of a preferred embodiment shouldnot be limited by any of the above-described exemplary embodiments, butshould be defined only in accordance with the following claims and theirequivalents.

What is claimed is:
 1. A mobile phone, comprising: a touchscreenincluding a backlight; a near field communication interface; amechanical button; at least one non-transitory memory storinginstructions; and one or more processors in communication with thetouchscreen, the near field communication interface, the mechanicalbutton, and the at least one non-transitory memory, wherein the one ormore processors execute the instructions to: receive, from a terminalutilizing the near field communication interface of the mobile phone, anear field communication signal; determine whether the mobile phone isoperating in a lock screen mode; determine whether the backlight of thetouchscreen of the mobile phone is powered off; after the receipt of thenear field communication signal from the terminal utilizing the nearfield communication interface of the mobile phone when the backlight ofthe touchscreen of the mobile phone is determined to be powered off:power on the backlight of the touchscreen of the mobile phone; after thereceipt of the near field communication signal from the terminalutilizing the near field communication interface of the mobile phonewhen the mobile phone is determined to be operating in the lock screenmode, and without necessitating any user input into the mobile phoneafter the receipt of the near field communication signal from theterminal utilizing the near field communication interface of the mobilephone: simultaneously display, via the touchscreen of the mobile phone,at least one card, at least a portion of a card number of the at leastone card, and an indication to enter a touch user input via themechanical button of the mobile phone; after the display, via thetouchscreen of the mobile phone, of the at least one card, the at leastportion of the card number of the at least one card, and the indicationto enter the touch user input via the mechanical button of the mobilephone: receive an indication of the touch input via the mechanicalbutton of the mobile phone; without necessitating any user input intothe mobile phone other than the touch user input via the mechanicalbutton of the mobile phone and a presentation of a face of a user afterthe display, via the touchscreen of the mobile phone, of the at leastone card, the at least portion of the card number of the at least onecard, and the indication to enter the touch user input via themechanical button of the mobile phone: capture the face, utilizing themobile phone, after the capture of the face utilizing the mobile phone,perform an analysis based on the capture of the face, and based on theanalysis, send, to the terminal utilizing the near field communicationinterface of the mobile phone, a first signal; and after sending, to theterminal utilizing the near field communication interface of the mobilephone, the first signal: receive a second signal, and after the receiptof the second signal: display, via the touchscreen of the mobile phone,a notification.
 2. The mobile phone of claim 1, wherein the one or moreprocessors execute the instructions to receive a user selectionindicating that the at least one card is a default card among aplurality of cards, wherein the at least one card is displayed via thetouchscreen, based on the user selection.
 3. The mobile phone of claim1, wherein the one or more processors further execute the instructionsto: display a settings interface, and receive a user selection to enableor disable a capability involving the display of the at least one cardwhen the mobile phone is determined to be operating in the lock screenmode, and wherein the at least one card is displayed when the mobilephone is determined to be operating in the lock screen mode, based onthe user selection.
 4. The mobile phone of claim 1, wherein the mobilephone is configured to remain in the lock screen mode after the captureof the face and further after the first signal is sent to the terminalutilizing the near field communication interface of the mobile phone. 5.The mobile phone of claim 1, wherein the mobile phone is configured suchthat the touch user input on the mechanical button includes adouble-click.
 6. The mobile phone of claim 1, wherein the mobile phoneis configured such that the touch user input serves to prevent anaccidental capture of the face.
 7. The mobile phone of claim 1, whereinthe mobile phone is configured such that the at least one card, the atleast portion of the card number of the at least one card, and theindication to enter the touch user input via the mechanical button ofthe mobile phone; are displayed via a lock screen.
 8. The mobile phoneof claim 7, wherein the mobile phone is configured such that the lockscreen is visually different from an application interface of anapplication that is configured to display the at least one card, the atleast portion of the card number of the at least one card, and theindication to enter the touch user input via the mechanical button ofthe mobile phone.
 9. The mobile phone of claim 7, wherein the mobilephone is configured such that the lock screen includes a visualindication that the mobile phone is operating in the lock screen mode.10. The mobile phone of claim 1, wherein the mobile phone is configuredto, after the touch user input via the mechanical button of the mobilephone: display an indication that the mobile phone is ready to capturethe face.
 11. The mobile phone of claim 1, wherein the mobile phone isconfigured to display an option to, as an alternative to thepresentation of the face of the user, enter a passcode for causing thefirst signal to be sent.
 12. The mobile phone of claim 1, wherein themobile phone is configured to, after the touch user input via themechanical button of the mobile phone: display an option to, as analternative to the presentation of the face of the user, enter apasscode for causing the first signal to be sent.
 13. The mobile phoneof claim 1, wherein the mobile phone is configured such that, other thanthe touch user input and, thereafter, the presentation of the face ofthe user, no other user input is required into the mobile phone afterthe receipt of the near field communication signal and before sendingthe first signal, in order to use the at least one card.
 14. The mobilephone of claim 13, wherein at least one of: the near field communicationinterface includes a near field communication interface adapter; the atleast one non-transitory memory includes a plurality of memories; the atleast one non-transitory memory includes a plurality of memories thateach store a different subset of the instructions; the at least onenon-transitory memory includes a single memory; the one or moreprocessors include a single processor; the one or more processorsinclude multiple processors; the one or more processors include multipleprocessors each configured to carry out different capabilities; afterthe receipt of the near field communication signal from the terminalutilizing the near field communication interface of the mobile phone, anadditional one or more operations is performed before it is determinedwhether the mobile phone is operating in the lock screen mode andwhether the backlight of the touchscreen of the mobile phone is poweredoff; it is determined whether the mobile phone is operating in the lockscreen mode before it is determined the backlight of the touchscreen ofthe mobile phone is powered off; it is determined whether the mobilephone is operating in the lock screen mode after it is determined thebacklight of the touchscreen of the mobile phone is powered off; themobile phone operates in the lock screen mode when the backlight of thetouchscreen of the mobile phone is powered off; the backlight of thetouchscreen of the mobile phone is powered off when the mobile phoneoperates in the lock screen mode; the backlight of the touchscreen ofthe mobile phone is powered on after the mobile phone being determinedto be operating in the lock screen mode; the backlight of thetouchscreen of the mobile phone is powered on only after the mobilephone being determined to be operating in the lock screen mode; the lockscreen mode includes a mode that prevents others from accessing themobile phone; the lock screen mode includes a mode that prevents othersfrom accessing one or more features of the mobile phone; the lock screenmode includes a mode that prevents others from accessing one or morefeatures of the mobile phone, while access to other features ispermitted; the near field communication signal includes a triggersignal; the determination that the backlight of the touchscreen of themobile phone is powered off includes a determination whether the mobilephone is in a standby mode; the determination that the backlight of thetouchscreen of the mobile phone is powered off includes a determinationwhether the mobile phone is in a sleep mode; the first signal includes acode; the first signal is sent via another interface separate from thenear field communication interface; the second signal includes aconfirmation; the second signal is received via another interfaceseparate from the near field communication interface; the use of the atleast one card is non-financial; transaction information is displayedsimultaneously with the indication; the at least portion of the cardnumber of the at least one card includes an entirety of the card number;the touch user input causes the face to be captured when presented; thetouch user input causes the face to be captured; the mobile phone ispart of a system that includes the terminal; or wherein the mobile phoneis configured for determining a location associated with the mobilephone; determining a presence of at least one other person at thelocation; and automatically displaying a graphical user interfaceassociated with the determined location and the determined presence ofthe at least one other person, wherein the mobile phone is furtherconfigured for determining that the location is proximate to apreviously identified item of interest; and displaying another graphicaluser interface associated with the determined location and thepreviously identified item of interest.
 15. The mobile phone of claim 1,wherein the mobile phone is configured such that the simultaneousdisplay is performed without necessitating any user input into themobile phone after the receipt of the near field communication signalwhen the mobile phone is determined to be operating in the lock screenmode, for reducing a technical problem of an undue duration ofinteraction with the terminal.
 16. The mobile phone of claim 1, whereinthe mobile phone is configured such that the simultaneous display occurswithout necessitating any user input into the mobile phone after thereceipt of the near field communication signal when the mobile phone isdetermined to be operating in the lock screen mode, for avoiding a needfor manual access of an application before the simultaneous display. 17.The mobile phone of claim 1, wherein the mobile phone is configured suchthat the simultaneous display occurs without necessitating any userinput into the mobile phone after the receipt of the near fieldcommunication signal when the mobile phone is determined to be operatingin the lock screen mode, for avoiding a need to manually unlock themobile phone before the simultaneously display.
 18. The mobile phone ofclaim 1, wherein the mobile phone is configured such that thesimultaneous display occurs without necessitating any user input intothe mobile phone after the receipt of the near field communicationsignal when the mobile phone is determined to be operating in the lockscreen mode, to avoid repeated instances of the analysis before thefirst signal is sent.
 19. The mobile phone of claim 1, wherein themobile phone is configured such that the simultaneous display occurswithout necessitating any user input into the mobile phone after thereceipt of the near field communication signal when the mobile phone isdetermined to be operating in the lock screen mode, to avoid, before thefirst signal is sent, unnecessary repeated instances of the analysisthat would otherwise be required to perform user authentication for bothunlocking the mobile phone and sending the first signal.
 20. The mobilephone of claim 1, wherein the mobile phone is configured such that thesimultaneous display occurs without necessitating any user input intothe mobile phone after the receipt of the near field communicationsignal when the mobile phone is determined to be operating in the lockscreen mode, so that only a single instance of the analysis is requiredfor sending the first signal when the mobile phone is determined to beoperating in the lock screen mode.
 21. The mobile phone of claim 1,wherein the mobile phone is configured such that the simultaneousdisplay is performed without necessitating any user input into themobile phone after the receipt of the near field communication signalwhen the mobile phone is determined to be operating in the lock screenmode, for reducing a technical problem of an undue duration ofinteraction with the terminal, that results from avoiding a need formanual access of an application before the simultaneous display.
 22. Themobile phone of claim 1, wherein the mobile phone is configured suchthat the simultaneous display occurs without necessitating any userinput into the mobile phone after the receipt of the near fieldcommunication signal when the mobile phone is determined to be operatingin the lock screen mode, for solving a technical problem of requiringunwarranted mobile phone battery and mobile phone processing resourceusage prior to the first signal being sent.
 23. The mobile phone ofclaim 1, wherein the mobile phone is configured such that thesimultaneous display is performed without necessitating any user inputinto the mobile phone after the receipt of the near field communicationsignal when the mobile phone is determined to be operating in the lockscreen mode, for avoiding, before the simultaneous display, userrequirements to unlock the mobile phone and access an application,thereby reducing technical problems involving an undue duration ofinteraction with the terminal and an unwarranted mobile phone batteryand mobile phone processing resource usage prior to the first signalbeing sent.
 24. The mobile phone of claim 1, wherein the mobile phone isconfigured such that no user input into the mobile phone is necessarybetween the receipt of the near field communication signal and thedisplay of the notification.
 25. The mobile phone of claim 1, whereinthe mobile phone is configured such that the first signal includes acode.
 26. The mobile phone of claim 1, wherein at least one of: saidnear field communication interface includes a near field communicationinterface adapter; said at least one non-transitory memory includes aplurality of memories; said at least one non-transitory memory includesa plurality of memories that each store a different subset of theinstructions; said at least one non-transitory memory includes a singlememory; said one or more processors include a single processor; said oneor more processors include multiple processors; said one or moreprocessors include multiple processors each configured to carry outdifferent capabilities; said indication of the touch input includes asignal that is received by the one or more processors in response to atleast one depression of the mechanical button; after the receipt of thenear field communication signal from the terminal utilizing the nearfield communication interface of the mobile phone, an additional one ormore operations is performed before it is determined whether the mobilephone is operating in the lock screen mode; after the receipt of thenear field communication signal from the terminal utilizing the nearfield communication interface of the mobile phone, an additional one ormore operations is performed before it is determined whether thebacklight of the touchscreen of the mobile phone is powered off; afterthe receipt of the near field communication signal from the terminalutilizing the near field communication interface of the mobile phone, nooperations are performed before it is determined whether the mobilephone is operating in the lock screen mode; after the receipt of thenear field communication signal from the terminal utilizing the nearfield communication interface of the mobile phone, no operations areperformed before it is determined whether the backlight of thetouchscreen of the mobile phone is powered off; said notificationincludes information associated with use of the at least one card; saidnotification includes information associated with use of the at leastone card including a location of the terminal; said notification doesnot include information associated with use of the at least one card;said near field communication signal includes a trigger signal; saidfirst signal includes a code; said first signal is sent via anotherinterface separate from the near field communication interface; saidfirst signal results from a user authorization; said first signalresults from an authorization; said first signal is capable of beingused for a subsequent authorization process; said first signal causes asubsequent authorization process; said first signal triggers asubsequent authorization process; said first signal results from a userverification or authentication; said first signal results from a userconfirmation prompt; said second signal includes a confirmation; saidsecond signal is in response to the first signal; said second signal isreceived after sending the first signal, by being received in responseto sending the first signal; said second signal is received via anotherinterface separate from the near field communication interface; saidlock screen mode includes a mode that prevents others from accessing themobile phone; said lock screen mode includes a mode that prevents othersfrom accessing one or more features of the mobile phone; said lockscreen mode includes a mode that prevents others from accessing one ormore features of the mobile phone, while access to other features ispermitted; said at least one card is a non-financial card; said at leastone card and the at least portion of the card number of the at least onecard are displayed before the first signal is sent; said mobile phone isdetermined to be operating in the lock screen mode in an absence of thereceipt of biometric input or identifier input; said simultaneouslydisplay occurs without necessitating any user input into the mobilephone after the receipt of the near field communication signal, whileallowing certain user input to be inputted after the receipt of the nearfield communication signal; said any user input into the mobile phone isnot required after the receipt of the near field communication signal sothat the simultaneous display occurs, but certain user input ispermitted; said any user input into the mobile phone is not necessaryafter the receipt of the near field communication signal so that thesimultaneous display occurs, but certain user input is permitted; saidat least portion of the card number of the at least one card includes anentirety of the card number; or said mobile phone is part of a systemthat includes the terminal; and wherein the mobile phone is configuredfor determining a location associated with the mobile phone; determininga presence of at least one other person at the location; andautomatically displaying a graphical user interface associated with thedetermined location and the determined presence of the at least oneother person, wherein the mobile phone is further configured fordetermining that the location is proximate to a previously identifieditem of interest; and displaying another graphical user interfaceassociated with the determined location and the previously identifieditem of interest.
 27. A mobile phone, comprising: a touchscreenincluding a backlight; a near field communication interface; at leastone non-transitory memory storing instructions; and one or moreprocessors in communication with the touchscreen, the near fieldcommunication interface, and the at least one non-transitory memory,wherein the one or more processors execute the instructions to: receive,from a terminal utilizing the near field communication interface of themobile phone, a near field communication signal; determine whether themobile phone is operating in a lock screen mode; determine whether thebacklight of the touchscreen of the mobile phone is powered off; afterthe receipt of the near field communication signal from the terminalutilizing the near field communication interface of the mobile phonewhen the backlight of the touchscreen of the mobile phone is determinedto be powered off: power on the backlight of the touchscreen of themobile phone; after the receipt of the near field communication signalfrom the terminal utilizing the near field communication interface ofthe mobile phone when the mobile phone is determined to be operating inthe lock screen mode, and without necessitating any user input into themobile phone after the receipt of the near field communication signalfrom the terminal utilizing the near field communication interface ofthe mobile phone: simultaneously display, via the touchscreen of themobile phone, at least one card, at least a portion of a card number ofthe at least one card, and an indication to scan a fingerprint via themobile phone; without necessitating any user input into the mobile phoneother than a fingerprint scan user input after the display, via thetouchscreen of the mobile phone, of the at least one card, the at leastportion of the card number of the at least one card, and the indicationto scan the fingerprint via the mobile phone: scan the fingerprint,utilizing the mobile phone, after the scan of the fingerprint utilizingthe mobile phone, perform an analysis based on the scan of thefingerprint, and based on the analysis, send, to the terminal utilizingthe near field communication interface of the mobile phone, a firstsignal; and after sending, to the terminal utilizing the near fieldcommunication interface of the mobile phone, the first signal: receive asecond signal, and after the receipt of the second signal: display, viathe touchscreen of the mobile phone, a notification.
 28. The mobilephone of claim 27, wherein the one or more processors execute theinstructions to receive a user selection indicating that the at leastone card is a default card among a plurality of cards, wherein the atleast one card is displayed via the touchscreen, based on the userselection.
 29. The mobile phone of claim 27, wherein the one or moreprocessors execute the instructions to: display a settings interface,and receive a user selection to enable or disable a capability involvingthe display of the at least one card when the mobile phone is determinedto be operating in the lock screen mode, and wherein the at least onecard is displayed when the mobile phone is determined to be operating inthe lock screen mode, based on the user selection.
 30. The mobile phoneof claim 27, wherein the mobile phone is configured to remain in thelock screen mode after the scan of the fingerprint and further after thefirst signal is sent to the terminal utilizing the near fieldcommunication interface of the mobile phone.
 31. The mobile phone ofclaim 27, wherein the mobile phone is configured such that the at leastone card, the at least portion of the card number of the at least onecard, and the indication to scan the fingerprint via the mobile phone;are displayed via a lock screen.
 32. The mobile phone of claim 31,wherein the mobile phone is configured such that the lock screen isvisually different from an application interface of an application thatis configured to display the at least one card, the at least portion ofthe card number of the at least one card, and the indication to scan thefingerprint via the mobile phone.
 33. The mobile phone of claim 31,wherein the mobile phone is configured such that the lock screenincludes a visual indication that the mobile phone is operating in thelock screen mode.
 34. The mobile phone of claim 27, wherein the mobilephone is configured such that, other than the fingerprint scan userinput, no other user input is required into the mobile phone after thereceipt of the near field communication signal and before sending thefirst signal, in order to use the at least one card.
 35. The mobilephone of claim 34, wherein at least one of: the near field communicationinterface includes a near field communication interface adapter; the atleast one non-transitory memory includes a plurality of memories; the atleast one non-transitory memory includes a plurality of memories thateach store a different subset of the instructions; the at least onenon-transitory memory includes a single memory; the one or moreprocessors include a single processor; the one or more processorsinclude multiple processors; the one or more processors include multipleprocessors each configured to carry out different capabilities; afterthe receipt of the near field communication signal from the terminalutilizing the near field communication interface of the mobile phone, anadditional one or more operations is performed before it is determinedwhether the mobile phone is operating in the lock screen mode andwhether the backlight of the touchscreen of the mobile phone is poweredoff; it is determined whether the mobile phone is operating in the lockscreen mode before it is determined the backlight of the touchscreen ofthe mobile phone is powered off; the mobile phone operates in the lockscreen mode when the backlight of the touchscreen of the mobile phone ispowered off; the backlight of the touchscreen of the mobile phone ispowered off when the mobile phone operates in the lock screen mode; itis determined whether the mobile phone is operating in the lock screenmode after it is determined the backlight of the touchscreen of themobile phone is powered off; the backlight of the touchscreen of themobile phone is powered on after the mobile phone being determined to beoperating in the lock screen mode; the backlight of the touchscreen ofthe mobile phone is powered on only after the mobile phone beingdetermined to be operating in the lock screen mode; the near fieldcommunication signal includes a trigger signal; the fingerprint isscanned using a fingerprint scanner is included as part of thetouchscreen; the fingerprint is scanned using a fingerprint scanner isseparate from the touchscreen; the determination that the backlight ofthe touchscreen of the mobile phone is powered off includes adetermination whether the mobile phone is in a standby mode; thedetermination that the backlight of the touchscreen of the mobile phoneis powered off includes a determination whether the mobile phone is in asleep mode; the first signal includes a code; the first signal is sentvia another interface separate from the near field communicationinterface; the second signal includes a confirmation; the second signalis received via another interface separate from the near fieldcommunication interface; the use of the at least one card isnon-financial; transaction information is displayed simultaneously withthe indication; the at least portion of the card number of the at leastone card includes an entirety of the card number; the user input otherthan the fingerprint scan user input, while not required, is capable ofbeing received; the user input other than the fingerprint scan userinput, while not necessary in a first operational scenario, is capableof being received in a second operational scenario; the user input otherthan the fingerprint scan user input, while not necessary, is capable ofbeing received; or the mobile phone is part of a system that includesthe terminal.
 36. The mobile phone of claim 27, wherein the mobile phoneis configured such that: the at least one card includes a credit card ora debit card; the card number includes a credit card number or a debitcard number; the first signal includes a financial transactionauthorization signal; the second signal includes a financial transactionreceipt signal; and the terminal includes a near point-of-sale terminal.37. The mobile phone of claim 27, wherein the mobile phone is configuredsuch that the simultaneous display is performed without necessitatingany user input into the mobile phone after the receipt of the near fieldcommunication signal when the mobile phone is determined to be operatingin the lock screen mode, for reducing a technical problem of an undueduration of interaction with the terminal.
 38. The mobile phone of claim27, wherein the mobile phone is configured such that the simultaneousdisplay occurs without necessitating any user input into the mobilephone after the receipt of the near field communication signal when themobile phone is determined to be operating in the lock screen mode, foravoiding a need for manual access of an application before thesimultaneous display.
 39. The mobile phone of claim 27, wherein themobile phone is configured such that the simultaneous display occurswithout necessitating any user input into the mobile phone after thereceipt of the near field communication signal when the mobile phone isdetermined to be operating in the lock screen mode, for avoiding a needto manually unlock the mobile phone before the simultaneously display.40. The mobile phone of claim 27, wherein the mobile phone is configuredsuch that the simultaneous display occurs without necessitating any userinput into the mobile phone after the receipt of the near fieldcommunication signal when the mobile phone is determined to be operatingin the lock screen mode, to avoid repeated instances of the analysisbefore the first signal is sent.
 41. The mobile phone of claim 27,wherein the mobile phone is configured such that the simultaneousdisplay is performed without necessitating any user input into themobile phone after the receipt of the near field communication signalwhen the mobile phone is determined to be operating in the lock screenmode, for reducing a technical problem of an undue duration ofinteraction with the terminal, that results from avoiding a need formanual access of an application before the simultaneous display.
 42. Themobile phone of claim 27, wherein the mobile phone is configured suchthat the simultaneous display occurs without necessitating any userinput into the mobile phone after the receipt of the near fieldcommunication signal when the mobile phone is determined to be operatingin the lock screen mode, for solving a technical problem of requiringunwarranted mobile phone battery and mobile phone processing resourceusage prior to the first signal being sent.
 43. The mobile phone ofclaim 27, wherein the mobile phone is configured such that no user inputinto the mobile phone is necessary between the receipt of the near fieldcommunication signal and the display of the notification.
 44. The mobilephone of claim 27, wherein the mobile phone is configured such that thefirst signal includes a code.
 45. The mobile phone of claim 27, whereinthe mobile phone is configured such that the simultaneous display isperformed without necessitating any user input into the mobile phoneafter the receipt of the near field communication signal when the mobilephone is determined to be operating in the lock screen mode, foravoiding, before the simultaneous display, user requirements to unlockthe mobile phone and access an application, thereby reducing technicalproblems involving an undue duration of interaction with the terminaland an unwarranted mobile phone battery and mobile phone processingresource usage prior to the first signal being sent.
 46. The mobilephone of claim 27, wherein the mobile phone is configured such that thesimultaneous display occurs without necessitating any user input intothe mobile phone after the receipt of the near field communicationsignal when the mobile phone is determined to be operating in the lockscreen mode, to avoid, before the first signal is sent, unnecessaryrepeated instances of the analysis that would otherwise be required toperform user authentication for both unlocking the mobile phone andsending the first signal.
 47. The mobile phone of claim 27, wherein themobile phone is configured such that the simultaneous display occurswithout necessitating any user input into the mobile phone after thereceipt of the near field communication signal when the mobile phone isdetermined to be operating in the lock screen mode, so that only asingle instance of the analysis is required for sending the first signalwhen the mobile phone is determined to be operating in the lock screenmode.
 48. A mobile phone, comprising: a touchscreen including abacklight; a near field communication interface; a mechanical button; atleast one non-transitory memory storing instructions; and one or moreprocessors in communication with the touchscreen, the near fieldcommunication interface, the mechanical button, and the at least onenon-transitory memory, wherein the one or more processors execute theinstructions to: receive, from a terminal utilizing the near fieldcommunication interface of the mobile phone, a near field communicationsignal; determine whether the mobile phone is operating in a lock screenmode; determine whether the backlight of the touchscreen of the mobilephone is powered off; after the receipt of the near field communicationsignal from the terminal utilizing the near field communicationinterface of the mobile phone when the backlight of the touchscreen ofthe mobile phone is determined to be powered off: power on the backlightof the touchscreen of the mobile phone; after the receipt of the nearfield communication signal from the terminal utilizing the near fieldcommunication interface of the mobile phone when the mobile phone isdetermined to be operating in the lock screen mode, and withoutnecessitating any user input into the mobile phone after the receipt ofthe near field communication signal from the terminal utilizing the nearfield communication interface of the mobile phone: simultaneouslydisplay, via the touchscreen of the mobile phone, at least one card, atleast a portion of a card number of the at least one card, and anindication to enter a touch user input via the mechanical button of themobile phone; after the display, via the touchscreen of the mobilephone, of the at least one card, the at least portion of the card numberof the at least one card, and the indication to enter the touch userinput via the mechanical button of the mobile phone: receive anindication of the touch input via the mechanical button of the mobilephone; without necessitating any user input into the mobile phone otherthan the touch user input via the mechanical button of the mobile phoneand a presentation of a face of a user after the display, via thetouchscreen of the mobile phone, of the at least one card, the at leastportion of the card number of the at least one card, and the indicationto enter the touch user input via the mechanical button of the mobilephone: capture the face, utilizing the mobile phone, after the captureof the face utilizing the mobile phone, perform an analysis based on thecapture of the face, and based on the analysis, send, to the terminalutilizing the near field communication interface of the mobile phone, afirst signal, where the mobile phone is configured to be in the lockscreen mode after the first signal is sent to the terminal utilizing thenear field communication interface of the mobile phone, until unlockuser input is detected; and after sending, to the terminal utilizing thenear field communication interface of the mobile phone, the firstsignal: receive a second signal, and after the receipt of the secondsignal: display, via the touchscreen of the mobile phone, anotification.
 49. The mobile phone of claim 48, wherein the mobile phoneis configured to: receive a user selection indicating that the at leastone card is a default card among a plurality of cards, wherein the atleast one card is displayed via the touchscreen, based on the userselection; after the touch user input via the mechanical button of themobile phone: display an indication that the mobile phone is ready tocapture the face; after the touch user input via the mechanical buttonof the mobile phone: display an option to, as an alternative to thepresentation of the face of the user, enter a passcode for causing thefirst signal to be sent; other than the touch user input and thepresentation of the face of the user, no other user input into themobile phone is required after the receipt of the near fieldcommunication signal and before sending the first signal, in order touse the at least one card; remain in the lock screen mode after thecapture of the face and further after the first signal is sent to theterminal utilizing the near field communication interface of the mobilephone, until another instance of the capture of the face.
 50. The mobilephone of claim 49, wherein the mobile phone is configured such that thetouch user input on the mechanical button includes a double-click toprevent an accidental capture of the face.
 51. The mobile phone of claim50, wherein the mobile phone is configured such that the simultaneousdisplay occurs without necessitating any user input into the mobilephone after the receipt of the near field communication signal when themobile phone is determined to be operating in the lock screen mode, toavoid, before the first signal is sent, unnecessary repeated instancesof the analysis that would otherwise be required to perform userauthentication for both unlocking the mobile phone and sending the firstsignal.
 52. The mobile phone of claim 48, wherein the mobile phone isconfigured such that the simultaneous display is performed withoutnecessitating any user input into the mobile phone after the receipt ofthe near field communication signal when the mobile phone is determinedto be operating in the lock screen mode, for avoiding, before thesimultaneous display, user requirements to unlock the mobile phone andaccess an application, thereby solving technical problems involving anundue duration of interaction with the terminal and an unwarrantedmobile phone battery and mobile phone processing resource usage prior tothe first signal being sent.
 53. The mobile phone of claim 48, whereinthe mobile phone is configured such that the simultaneous display occurswithout necessitating any user input into the mobile phone after thereceipt of the near field communication signal when the mobile phone isdetermined to be operating in the lock screen mode, so that only asingle instance of the analysis is required for sending the first signalwhen the mobile phone is determined to be operating in the lock screenmode.
 54. A mobile phone, comprising: a touchscreen including abacklight; a near field communication interface; at least onenon-transitory memory storing instructions; and one or more processorsin communication with the touchscreen, the near field communicationinterface, and the at least one non-transitory memory, wherein the oneor more processors execute the instructions to: receive, from a terminalutilizing the near field communication interface of the mobile phone, anear field communication signal; determine whether the mobile phone isoperating in a lock screen mode; determine whether the backlight of thetouchscreen of the mobile phone is powered off; after the receipt of thenear field communication signal from the terminal utilizing the nearfield communication interface of the mobile phone when the backlight ofthe touchscreen of the mobile phone is determined to be powered off:power on the backlight of the touchscreen of the mobile phone; after thereceipt of the near field communication signal from the terminalutilizing the near field communication interface of the mobile phonewhen the mobile phone is determined to be operating in the lock screenmode, and without necessitating any user input into the mobile phoneafter the receipt of the near field communication signal from theterminal utilizing the near field communication interface of the mobilephone: simultaneously display, via the touchscreen of the mobile phone,at least one card, at least a portion of a card number of the at leastone card, and an indication to scan a fingerprint via the mobile phone;without necessitating any user input into the mobile phone other than afingerprint scan user input after the display, via the touchscreen ofthe mobile phone, of the at least one card, the at least portion of thecard number of the at least one card, and the indication to scan thefingerprint via the mobile phone: scan the fingerprint, utilizing themobile phone, after the scan of the fingerprint utilizing the mobilephone, perform an analysis based on the scan of the fingerprint, andbased on the analysis, send, to the terminal utilizing the near fieldcommunication interface of the mobile phone, a first signal, where themobile phone is configured to be in the lock screen mode after the firstsignal is sent to the terminal utilizing the near field communicationinterface of the mobile phone, until unlock user input is detected; andafter sending, to the terminal utilizing the near field communicationinterface of the mobile phone, the first signal: receive a secondsignal, and after the receipt of the second signal: display, via thetouchscreen of the mobile phone, a notification.
 55. The mobile phone ofclaim 54, wherein the mobile phone is configured to: receive a userselection indicating that the at least one card is a default card amonga plurality of cards, wherein the at least one card is displayed via thetouchscreen, based on the user selection; and other than the fingerprintscan user input, no other user input is required into the mobile phoneafter the receipt of the near field communication signal and beforesending the first signal, in order to use the at least one card.
 56. Themobile phone of claim 55, wherein the mobile phone is configured suchthat the unlock user input includes another instance of the fingerprintscan user input.
 57. The mobile phone of claim 56, wherein the mobilephone is configured such that the simultaneous display occurs withoutnecessitating any user input into the mobile phone after the receipt ofthe near field communication signal when the mobile phone is determinedto be operating in the lock screen mode, so that only a single instanceof the analysis is required for sending the first signal when the mobilephone is determined to be operating in the lock screen mode.
 58. Themobile phone of claim 54, wherein the mobile phone is configured suchthat the simultaneous display is performed without necessitating anyuser input into the mobile phone after the receipt of the near fieldcommunication signal when the mobile phone is determined to be operatingin the lock screen mode, for avoiding, before the simultaneous display,user requirements to unlock the mobile phone and access an application,thereby solving technical problems involving an undue duration ofinteraction with the terminal and an unwarranted mobile phone batteryand mobile phone processing resource usage prior to the first signalbeing sent.
 59. The mobile phone of claim 54, wherein the mobile phoneis configured such that the simultaneous display occurs withoutnecessitating any user input into the mobile phone after the receipt ofthe near field communication signal when the mobile phone is determinedto be operating in the lock screen mode, to avoid, before the firstsignal is sent, unnecessary repeated instances of the analysis thatwould otherwise be required to perform user authentication for bothunlocking the mobile phone and sending the first signal.
 60. A mobilephone-implement method, comprising: receiving, from a terminal utilizinga near field communication interface of a mobile phone, a near fieldcommunication signal; activating a backlight of a touchscreen of themobile phone, in response to the receipt of the near field communicationsignal from the terminal utilizing the near field communicationinterface of the mobile phone; simultaneously displaying, in a lockscreen mode of the mobile phone and via the touchscreen of the mobilephone: at least one card, at least a portion of a card number of the atleast one card, and an indication to enter a touch user input via amechanical button of the mobile phone, in response to the receipt of thenear field communication signal from the terminal utilizing the nearfield communication interface of the mobile phone, and withoutnecessitating any user input into the mobile phone after the receipt ofthe near field communication signal from the terminal utilizing the nearfield communication interface of the mobile phone; receiving anindication of the touch input via the mechanical button of the mobilephone; without necessitating any user input into the mobile phone otherthan the touch user input via the mechanical button of the mobile phoneand a presentation of a face of a user after the display, in the lockscreen mode of the mobile phone and via the touchscreen of the mobilephone, of the at least one card, the at least portion of the card numberof the at least one card, and the indication to enter the touch userinput via the mechanical button of the mobile phone: capturing the face,utilizing the mobile phone, in response to the capture of the faceutilizing the mobile phone, performing an analysis based on the captureof the face, utilizing one or more processors of the mobile phone, andbased on the analysis, sending, to the terminal utilizing the near fieldcommunication interface of the mobile phone, a first signal; receiving asecond signal; and displaying, via the touchscreen of the mobile phone,a notification.
 61. The mobile phone-implemented method of claim 60, andfurther comprising: receiving a user selection indicating that the atleast one card is a default card among a plurality of cards, wherein theat least one card is displayed via the touchscreen, based on the userselection; displaying an indication that the mobile phone is ready tocapture the face, in response to the touch user input via the mechanicalbutton of the mobile phone; and displaying an option to enter a passcodefor causing the first signal to be sent.
 62. The mobilephone-implemented method of claim 61, wherein the simultaneous displayis performed without necessitating any user input into the mobile phonein the lock screen mode after the receipt of the near fieldcommunication signal, for avoiding, before the simultaneous display,user requirements to unlock the mobile phone and access an application,thereby solving technical problems involving an undue duration ofinteraction with the terminal and an unwarranted mobile phone batteryand mobile phone processing resource usage prior to the first signalbeing sent.
 63. The mobile phone-implemented method of claim 62, whereinthe mobile phone is in the lock screen mode upon the receipt of the nearfield communication signal from the terminal utilizing the near fieldcommunication interface of the mobile phone.
 64. The mobilephone-implemented method of claim 62, wherein the mobile phone remainsin the lock screen mode after the capture of the face and further afterthe first signal is sent to the terminal utilizing the near fieldcommunication interface of the mobile phone, until another instance ofthe capture of the face.
 65. The mobile phone-implemented method ofclaim 62, wherein the touch user input prevents an accidental capture ofthe face.
 66. A mobile phone-implemented method, comprising: receiving,from a terminal utilizing a near field communication interface of amobile phone, a near field communication signal; activating a backlightof a touchscreen of the mobile phone, in response to the receipt of thenear field communication signal from the terminal utilizing the nearfield communication interface of the mobile phone; simultaneouslydisplaying, in a lock screen mode of the mobile phone and via thetouchscreen of the mobile phone: at least one card, at least a portionof a card number of the at least one card, and an indication to scan afingerprint via the mobile phone, in response to the receipt of the nearfield communication signal from the terminal utilizing the near fieldcommunication interface of the mobile phone, and without necessitatingany user input into the mobile phone after the receipt of the near fieldcommunication signal from the terminal utilizing the near fieldcommunication interface of the mobile phone: without necessitating anyuser input into the mobile phone other than a fingerprint scan userinput after the display, in the lock screen mode of the mobile phone andvia the touchscreen of the mobile phone, of the at least one card, theat least portion of the card number of the at least one card, and theindication to scan the fingerprint via the mobile phone: scanning thefingerprint, utilizing the mobile phone, in response to the scan of thefingerprint utilizing the mobile phone, performing an analysis based onthe scan of the fingerprint, utilizing one or more processors of themobile phone, and based on the analysis, sending, to the terminalutilizing the near field communication interface of the mobile phone, afirst signal; receiving a second signal; and displaying, via thetouchscreen of the mobile phone, a notification.
 67. The mobilephone-implemented method of claim 66, and further comprising: receivinga user selection indicating that the at least one card is a default cardamong a plurality of cards, wherein the at least one card is displayedvia the touchscreen, based on the user selection.
 68. The mobilephone-implemented method of claim 67, wherein the simultaneous displayis performed without necessitating any user input into the mobile phonein the lock screen mode after the receipt of the near fieldcommunication signal, for avoiding, before the simultaneous display,user requirements to unlock the mobile phone and access an application,thereby solving technical problems involving an undue duration ofinteraction with the terminal and an unwarranted mobile phone batteryand mobile phone processing resource usage prior to the first signalbeing sent.